Closed joshgillies closed 8 years ago
This is deliberate, so that the end user is in control of the JSS version. Otherwise this loader will have to keep updating for no reason, just to stay up to date with JSS.
Interesting, I wouldn't say I'm against this decision, but will highlight that it doesn't seem to be a common practice amongst other Webpack loaders.
I guess a point for maintaining the version relative to the loader is to better manage API changes that could take place within JSS?
Not sure if there was a reason for excluding it in the first place?