-
Notifications
You must be signed in to change notification settings - Fork 106
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
Update docs for v2.0.0 #115
Conversation
README.md
Outdated
|
||
<br> | ||
## Migrating from version 1.x.y to 2.x.y | ||
Starting on version 2.0.0, when creating a new instance of `BundleTracker`, the usage of the `path` parameter has been fixed and it's now being used to generate the output path for the stats file, together with the `filename` parameter. On version 2.0.0, if the `path` parameter is ommited from the constuctor call, it will use its default value and may end up placing the stats file inside an incorrect directory. To avoid that, when migrating, double-check if the file placement is as expected. The usage of these parameters is documented [here](#usage) and [here](#options). |
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.
"it will use its default value and may end up placing the stats file inside an incorrect directory." clarify please what the default is: where it places the file.
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.
Updated this one and the table on the footer to clarify the behavior (that it'll use the output.path
before trying to use root directory).
README.md
Outdated
@@ -39,13 +35,13 @@ module.exports = { | |||
plugins: [ | |||
new BundleTracker({ | |||
path: __dirname, | |||
filename: './assets/webpack-stats.json', | |||
filename: 'assets/webpack-stats.json', |
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.
perhaps we should always reject dirs in filename?
for the path to work here, we can do path.join(__dirname, 'assets')
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.
Isolated this behavior on 340dc1a, so we can easily revert if we decide not moving forward with it.
@JanMalte could you please review too? |
No description provided.