-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Proposal: explicit query param imports for non-JS/CSS assets #5842
Comments
We've already implemented this feature (in a slightly different way) for SVGs: https://facebook.github.io/create-react-app/docs/adding-images-fonts-and-files#adding-svgs |
@iansu but this proposal seems to be more browser compatible. (like uri) |
@xiaoxiangmoe how will other users migrate if they load multiple types in one import statement? |
@miraage load multiple types in one import statement will also work without query params |
@xiaoxiangmoe Just because you use URLs doesn't make it any more "browser compatible". :-) |
We'll want to watch this: https://github.com/sebmarkbage/ecmascript-asset-references |
@gaearon see: parcel-bundler/parcel#2306 I want it could be zero configuration. |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
Previous Proposal
see @gaearon 's Proposal: explicit named imports for non-JS/CSS assets #3722
Proposal
see ECMAScript Modules - Node.js | URL based paths:
docHtml
anddocHtmlText
will load as different type by different webpack loader.Concerns
The text was updated successfully, but these errors were encountered: