We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
http://2ality.com/2017/04/transpiling-dependencies-babel.html#extended-versions-of-pkgesnext
webpack.config.js:
webpack.config.js
resolve: { mainFields: ["esnext.main"] }
package.json:
package.json
{ "esnext": { "main": "main-esnext.js", "browser": "browser-specific-main-esnext.js" } }
What is the expected behavior?
support nested properties in resolve.mainFields
What is motivation or use case for adding/changing the behavior?
deliver un-transpiled source code for different platforms
How should this be implemented in your opinion?
https://github.com/rauschma/esnext-demo#rationale-and-future
Are you willing to work on this yourself?
yes
The text was updated successfully, but these errors were encountered:
webpack already supports nested main fields:
mainFields: [["esnext", "main"], "esnext", "main"],
Support for paths will not be added because it would break builds were the dot is intentional ("esnext.main" is a valid field name).
Sorry, something went wrong.
Great!
ResolveTypes
No branches or pull requests
Feature request
http://2ality.com/2017/04/transpiling-dependencies-babel.html#extended-versions-of-pkgesnext
webpack.config.js
:package.json
:What is the expected behavior?
support nested properties in resolve.mainFields
What is motivation or use case for adding/changing the behavior?
deliver un-transpiled source code for different platforms
How should this be implemented in your opinion?
https://github.com/rauschma/esnext-demo#rationale-and-future
Are you willing to work on this yourself?
yes
The text was updated successfully, but these errors were encountered: