You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
I'm guessing it's installing 1.12.14 because it's the latest stable version? What do you mean by 'the consumer has webpack 2.1.0-beta.4"? Is it installed globally?
The reason will be displayed to describe this comment to others. Learn more.
The commit says it support webpack 2 but how should I do to actually get that installed? If I put the beta version in package.json it will install 1.12.14 as you say. Maybe it will work when it's not beta anymore?. If it were a peer dependency it would be up to the "consumer" to provide the plugin with a version.. just my thoughts then I guess it would have worked even with the beta version
The reason will be displayed to describe this comment to others. Learn more.
You make a good point about making webpack a peer dependency. Might be the better option.
I just installed webpack beta with 'npm install [email protected] --save' and that does properly install the beta version, but aurelia-webpack-plugin will indeed still use 1.12.14 internally (and throw the 'No module factory available for dependency type: ContextElementDependency' exception).
dc945fe
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.
@martijnboland why would this support webpack 2? It's still installing
1.12.14
even if the consumer has"webpack": "^2.1.0-beta.4"
Should this be under
peerDependencies
?dc945fe
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.
I'm guessing it's installing 1.12.14 because it's the latest stable version? What do you mean by 'the consumer has webpack 2.1.0-beta.4"? Is it installed globally?
dc945fe
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.
The commit says it support webpack 2 but how should I do to actually get that installed? If I put the beta version in
package.json
it will install 1.12.14 as you say. Maybe it will work when it's not beta anymore?. If it were a peer dependency it would be up to the "consumer" to provide the plugin with a version.. just my thoughts then I guess it would have worked even with the beta versiondc945fe
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.
You make a good point about making webpack a peer dependency. Might be the better option.
I just installed webpack beta with 'npm install [email protected] --save' and that does properly install the beta version, but aurelia-webpack-plugin will indeed still use 1.12.14 internally (and throw the 'No module factory available for dependency type: ContextElementDependency' exception).