-
-
Notifications
You must be signed in to change notification settings - Fork 608
version 1.0 #742
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
version 1.0 #742
Conversation
# Conflicts: # test/simpleTest.js
BREAKING CHANGE: remove `minimize` option
BREAKING CHANGE: remove `module` option, use `modules` option instead
BREAKING CHANGE: remove `camelcase` option, use `camelCase` option instead
BREAKING CHANGE: remove `root` option, use `postcss-loader` with `postcss-url` plugin instead
BREAKING CHANGE: remove `alias` option, use `webpack` `resolve.alias` option
BREAKING CHANGE: minimum require `nodejs` version is `6.9`
/cc @ai Can you help me with better integration |
Sure. What I need to look? |
@ai need find way how use In short: need add example |
👍 will send you a PR in next few days |
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.
A few notes. Should webpack-defaults be merged into this repo before or after this PR is merged?
@@ -7,20 +7,20 @@ matrix: | |||
fast_finish: true | |||
include: | |||
- os: linux | |||
node_js: "7" | |||
env: WEBPACK_VERSION="2.2.0" JOB_PART=lint | |||
node_js: "10" |
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.
can we ditch travis and get on circle CI?
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.
@shellscape let's do this in other PR
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.
OK
var root = query.root; | ||
var moduleMode = query.modules || query.module; | ||
var camelCaseKeys = query.camelCase || query.camelcase; | ||
var moduleMode = query.modules; |
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.
because this is a refactor, shouldn't we use const
and let
instead?
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.
@shellscape also let's do it other PR, when we ship webpack-default in this repo
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.
OK
package.json
Outdated
@@ -36,6 +34,9 @@ | |||
"should": "^11.1.2", | |||
"standard-version": "^4.0.0" | |||
}, | |||
"peerDependencies": { | |||
"webpack": "^3.0.0 || ^4.0.0" |
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.
new major versions of webpack-contrib and webpack org modules are only supporting webpack@4 moving forward. since this is a new major version, we should drop webpack@3 support.
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.
Agree with Andrew, it's harder to keep compat when things move forward too
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.
@shellscape i think we can update webpack-default after merge this PR, because problem with |
BREAKING CHANGE: minimum require `webpack` version is `4`
Codecov Report
@@ Coverage Diff @@
## master #742 +/- ##
==========================================
- Coverage 98.43% 98.25% -0.19%
==========================================
Files 11 10 -1
Lines 384 344 -40
Branches 90 76 -14
==========================================
- Hits 378 338 -40
Misses 6 6
Continue to review full report at Codecov.
|
There are few more breaking changes possible, but that should be considered carefully: Dropping
|
@@ -36,6 +34,9 @@ | |||
"should": "^11.1.2", | |||
"standard-version": "^4.0.0" | |||
}, | |||
"peerDependencies": { | |||
"webpack": "^4.0.0" |
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.
Not sure about this. The codebase does not require('webpack')
. I understand that you added this to avoid runtime errors when webpack's version is not the expected one but I don't think this is the correct solution.
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.
@ooflorent we use this for all webpack-contrib repos, better create issue in webpack-default
about this.
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.
@ooflorent Also it is prevent problem with using webpack api between version, if somebody want use css-loader
on webpack@3
, they can use old version
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.
yeah it's a standard for webpack-defaults. that peerDep on webpack has been in defaults for a very long time. along with the Requirements
section in the defaults README, this serves as a warning to keep people on supported versions of webpack. new major versions of loaders/plugins/utils are webpack@4+ and Node 6+ only.
Let's do it and do |
What kind of change does this PR introduce?
refactor
Did you add tests for your changes?
already exists
If relevant, did you update the README?
yes
Summary
Roadmap:
1.0.0
version.2.0.0
version.Does this PR introduce a breaking change?
yes
Other information
Let's do it
fixes #691 fixes #265 fixes #688 fixes #732