-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
🙋 Aliasing modules -- react -> preact-compat etc. #832
Labels
Comments
Would really love this. Parcel is very cool, but I've kind of screwed myself out of its use in the short term by using Webpack's aliasing so much. |
See #850 for an implementation of aliases as part of our new resolver. |
no work |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is impossible to use parcel with preact-compat because it requires being able to alias all references to 'react' and 'react-dom' to 'preact-compat'. It is possible to do this for local package using
browser
inpackage.json
, but does not work when including external React components.🤔 Expected Behavior
Add an alias field in, say,
package.json
, likeWhich would then replace all references to
react
withpreact-compat
etc.😯 Current Behavior
Using
browser
field, I can replace local import/requires successfully, but when importing, sayreact-apollo
, it doesn't replace there.🔦 Context
I know there was an issue #25 for this but it got locked and I haven't seen any further discussion about it, but this is quite inconvenient for people trying to use preact. I think it was a bad decision to completely delete all discussion about current workarounds as now people have no reference on what to do until this gets implemented natively.
Workaround for now
The workaround I found is to make symbolic links in the
node_modules
folder so thatnode_modules/react
andnode_modules/react-dom
both link tonode_modules/preact-compat
.The text was updated successfully, but these errors were encountered: