-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2.0 #266
Release 2.0 #266
Conversation
docs/BLOCK-CREATION.md
Outdated
*Deprecated. This feature will be removed soon. Use `match()` and `context.match` instead.* | ||
|
||
The `context.fileType` is a mapping from MIME type (`application/javascript`, `text/css`, ...) to a regular expression used for matching filenames. You can find the default file types and the extensions they match [here](https://github.com/andywer/webpack-blocks/blob/master/packages/core/lib/defaultFileTypes.js). | ||
Initially it will contain a `webpack` instance. If you are using [hooks](#hooks) you might want to put custom metadata into the context and use it in the `post` hook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👌
1f23d65
to
9d1535b
Compare
PS: Changed the PR title. |
Did someone change the PR title again? "Release 2.0" is not a good title for this PR... |
@vlad-zhukov Why not merge this already as "Remove deprecated features"? Multiple short PRs are easier to review and comprehend than few large ones :) I think if we add new code in this PR, too, than it will get quite messy, because of the large number of changed lines. |
Because these changes have been already reviewed and merged into this branch. I am not going to push commits into this branch directly, only through PRs! 😏 |
Ahhh, now I get it 😉 I would suggest, though, that we either So no one can accidentally merge this prematurely. You know, accidents happen... 😅 Thoughts? |
I would like to have this PR opened to keep track of certain stuff. Added a WIP note, is it ok? And I've already created a 2.0.0 milestone earlier today. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a release PR and will not be merged until all its changes are done.
Blocking the PR for now.
Ok. Just did a "request changes" to prevent merging for now. Btw, thank you guys for your efforts! You are really moving the project forward 😊 |
Ready for the 1st alpha I guess! |
Sure! Can do, but not before tonight 😉 |
Sorry, didn't realize it was a question... 😅 Let's publish from this feature branch for the alpha release. |
Published as @Lavoaster |
Thanks @andywer @vlad-zhukov Upgraded this and to webpack 4.0 the other day and it all went pretty smooth, all I really needed to do was add the |
@Lavoaster can you help me with a sample config for webpack 4.0? |
@vpsouza Do you mean a sample config with webpack-blocks? If so, I have one in my project. It's a refactored version of the webpack config from create-react-app. Although it's not perfect and uses webpack-blocks v1.0, you may find it useful. |
@andywer @vlad-zhukov @zcei BTW, I had an idea of creating a preset with blocks for React apps |
@dmitmel Sure. Feel free to share it in the gitter chat room :) |
Loaders updates (especially css-loader)
* Support for babel-loader@8 / babel@7 * Fix babel@7 references in tests and sample-app
* Upgrade a few deps * Downgrade ava and update almost all other deps * Downgrade jsdom back to v11 * Update more deps
WIP, DON'T MERGEHere we are working on a new major release according to the 2.0 roadmap. Use this branch as the base for new PRs.