Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
README.md | 2017-01-27 | 2.0 kB | |
v0.4 - A lot of small improvements source code.tar.gz | 2017-01-27 | 37.2 kB | |
v0.4 - A lot of small improvements source code.zip | 2017-01-27 | 90.7 kB | |
Totals: 3 Items | 129.8 kB | 0 |
Another step towards v1.0, containing one potentially breaking change:
The default CSS loader does not exclude the node_modules/
directory anymore. So you can now just require('some-other-package/stylesheet.css')
without additional configuration.
As the 1.0 release is getting closer I would like to encourage you to provide feedback, so we get to know what works well and what has to be improved.
Please share your experiences when using webpack-blocks, no matter if you encounter any problems or everything worked just fine right away! 👍
How to upgrade
Just open your package.json
and upgrade the @webpack-blocks/*
dependencies to ^0.4.0
. Then run npm install
/ yarn
.
Make sure you update all webpack-block packages at once, since the new default CSS loader behavior made changes in css-modules
and postcss
blocks necessary as well.
Changes
- Breaking change: Default CSS loader does not exclude
node_modules/
anymore - Added
createConfig.vanilla()
(#80, #95) - Made
dev-server
composable (#78)
Under the hood:
- Added webpackVersion
to context
- Using webpack-merge
v2.3 instead of v0.14
- Using webpack
v2.2 instead of the RC (webpack2
and related blocks only, of course)
- Fixed: The config object passed to blocks as parameter could contain duplicate values (#79)
- Added application/x-typescript
file type
- Added text/x-less
file type
News
Looking for TypeScript support? Then there is good news: @jvanbruegge just added the typescript and tslint blocks.
Check 'em out if you would like to give static typing a try 😉