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
{{ message }}
This repository has been archived by the owner on Aug 8, 2019. It is now read-only.
In the migrating guide, it says root and others are replaced by resolve.modules. But in the above Wiki, they are still there and not mentioned as deprecated. The above link was found by Googling, and the URL seems like it would be pointing at the latest docs.
Webpack configuration has always been error prone because of the multitudes of versions combined with tutorials and docs that don't mention specific versions.
Thinking out loud, what about using a version identifier in the config file, or an option to specify when version you intend to load?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
https://github.com/webpack/docs/wiki/configuration
In the migrating guide, it says root and others are replaced by resolve.modules. But in the above Wiki, they are still there and not mentioned as deprecated. The above link was found by Googling, and the URL seems like it would be pointing at the latest docs.
https://webpack.js.org/guides/migrating/
Webpack configuration has always been error prone because of the multitudes of versions combined with tutorials and docs that don't mention specific versions.
Thinking out loud, what about using a version identifier in the config file, or an option to specify when version you intend to load?
The text was updated successfully, but these errors were encountered: