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
microbundle uses source to identify the pre-Babel source code of a module, which could be a problem if the bundle config for the consumer doesn't match the source
Is there an RFC for using source in imports like there is for jsnext or module? Seems safer to treat as reserved for internal use of the package.
The text was updated successfully, but these errors were encountered:
microbundle uses source to identify the pre-Babel source code of a module, which could be a problem if the bundle config for the consumer doesn't match the source
We should be using the actual babel config of that package in this case.
Is there an RFC for using source in imports
There is no spec for package.json that actually reflects the current usage.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.
Seems like trying to use package.json's source field could be a source of issues:
parcel/src/Resolver.js
Line 279 in 98a293f
microbundle
usessource
to identify the pre-Babel source code of a module, which could be a problem if the bundle config for the consumer doesn't match the sourcesource
in imports like there is forjsnext
ormodule
? Seems safer to treat as reserved for internal use of the package.The text was updated successfully, but these errors were encountered: