Skip to content

Releases: stoikerty/dev-toolkit

Update to Babel 7, improve templates

12 Oct 10:34
Compare
Choose a tag to compare
  • updates templates to make webpack customization clearer
  • updates various dependencies such as webpack
  • updates all packages to use Babel 7
  • clarify node-version support by using .nvmrc

This update includes v2 of babel-runner and babel-preset-dev-toolkit since they were directly affected due to the switch to Babel 7.

update templates

25 Sep 10:27
c3bfbfb
Compare
Choose a tag to compare

updates templates to use correct webpack convention (rules instead of loaders)

Add serverless template

14 Sep 12:54
eabe2ea
Compare
Choose a tag to compare

This update adds a serverless template with additional support for the existing programmatic usage. If something isn't quite right, you will also get helpful errors which point out how the file should be written (that it needs to be a promise).

You are now able to specify an entry point for preRendering like so:

// Example of programmatic usage of dev-toolkit with a serverless-type application
require('dev-toolkit').default({
  command: 'preRender',
  options: {
    // Use the function from the entry point instead of `preRender` from `src/server/index`
    preRenderEntryPoint: path.resolve(process.cwd(), 'src/server/preRender'),
    // silence any console logging
    silent: true,
  },
});

exit with correct error-code, update dependencies

23 Aug 12:45
f2897f7
Compare
Choose a tag to compare

When an errors occured, dev-toolkit would log the error but not exit with the right error code.
It will now correctly exit with 1 when an error occurs.

Also updates to the latest webpack version as well as some other minor dependency updates.

Add `removeBuildFolder` option

23 Jul 10:30
Compare
Choose a tag to compare

In dev-toolkit.config.js, an option has been added to prevent removing the previous build folder.

module.exports = {
  devToolkit: { removeBuildFolder: false },
};

fixes a warning emit by `assets-webpack-plugin`

20 Jun 16:09
7474c20
Compare
Choose a tag to compare

fixes warning DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead

Fix bug related to dynamic `import()`-statements

31 May 14:16
5edcecc
Compare
Choose a tag to compare

When using NODE_ENV test, dynamic import statements wouldn't work properly. The related babel-preset was being declared twice due to an if-condition in the react-app preset.

This release fixes that issue.

Overall update of all dependencies

11 May 15:53
15e2951
Compare
Choose a tag to compare
Sanity update dependencies (#60)

* update all dependencies and release, release dev-toolkit as beta first

* bump to v7.0.1-2

* use `format` as separate npm command

* use format command

* bump version to 7.0.1

* update travis file and lint commands

* remove some unused tests

* bump to 7.0.2

* update paths in travis file

Add support for jsx-control-statements

06 Apr 13:53
Compare
Choose a tag to compare

Adds support for jsx-control-statements and make sure statements don't throw eslint-errors thanks to react/jsx-no-undef.

Release dev-toolkit v7 - Update to Webpack 4

06 Apr 13:57
Compare
Choose a tag to compare

With the update to v7 of dev-toolkit, the API for dev-toolkit.config has changed slightly.
The config key webpack.loaders has changed to webpack.rules.

See the with-sass template or the changes from the PR.

Updating to the latest version of dev-toolkit should be quite straightforward, unless you have a lot of webpack-plugins. We have updated webpack to v4 which brings a number of under-the-hood improvements. There are also some things one needs to be aware of, I've listed them below.


The vulnerabilities that snyk is reporting on have not gone away completely, but they should as far as I know not be anything to worry about in the case of regular usage of dev-toolkit as a tool. Snyk reports them as low vulnerabilities. They persist in the latest version of webpack (v4.5.0 right now) and it's impossible to make the warnings go away until the following issues have been resolved:
webpack/watchpack#63
fsevents/fsevents#187

If you are seeing warnings such as DeprecationWarning: Tapable.plugin is deprecated. then you should know that several plugins or settings still emit those warnings and are also nothing to worry about. For more information please see this PR:
webpack/webpack#6568