Releases: networkteam/nwt-frontend-scripts
v6.0.5
What's Changed
- Feature:
--noLivereloadflag for dev setup by @Rasmizzle in #26 - Webpack Test-Config: Ignore TS-Linting in node_modules by @Rasmizzle in #25
Full Changelog: v6.0.4...v6.0.5
v6.0.4
Switches out merging mechanis of webpack plugins merge.
This is an improvement and also a bugfix.
Improvement:
-
When a plugin is defined in custom webpack config that is already defined in
common.webpack.jsit is treated as one plugin that takes the default config and merges config of custom Webpack-Plugin onto it. This now also effects deeply nested configurations. -
added tests for feature
Bugfix:
- Fixes a bug where custom defined plugins in config would not be initialized
Note:
Deeply merging constructors only goes so far. If a default value of any used plugin in custom webpack config is initialized then it will overwrite the value defined in default config.
TypeScript Linting: exclude node_modules
- excludes ´node_modules` from TS Linter
- added path to
tsconfig.jsonto ForkTsCheckerWebpackPlugin
Initialize Webpack Plugins only once
When a plugin is defined in custom Webpack Config that is already defined in common.webpack.js it is treated as two seperate plugins that are both being initialized.
With this change this behaviour changes the following way:
When a plugin is defined in custom webpack config that is already defined in common.webpack.js it is treated as one plugin that takes the default config and merges config of custom Webpack-Plugin onto it.
This makes it possible to overwrite certain behaviour of frontend-scripts.
Readd support for .env
adds fallback for env variables if not found in package.json
- readded readable env keys:
BASE_PACKAGE_NAMESITE_PACKAGE_NAME
Use sass (Dart SASS) instead of node-sass
As it becomes more and more troublesome to install node-sass on modern platforms and node-sass is deprecated anyway, we now switch to the sass package which is a pure JS Sass compiler.
There are some possible issues with existing projects:
- The performance is a little worse for larger Sass files
- There
mightwill be incompatibilities, one that we found while testing was:- Using Sass Syntax in
.cssfiles was apparently ok withnode-sassbutsassthrows an error in these cases
- Using Sass Syntax in
v5.2.0
What's Changed
- Close compiler after run by @suffle in #12
- Output brotli compressed assets by @christophlehmann in #9
New Contributors
- @suffle made their first contribution in #12
- @christophlehmann made their first contribution in #9
Full Changelog: v5.0.1...5.2.0
Support TypeScript modules and tests
v5.0.1 Bump version