-
Notifications
You must be signed in to change notification settings - Fork 26
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
Replace alias in dependencies? #25
Comments
I'm having an almost identical problem but with trying to use
How do we make Aliasify cycle not just our source files, but the dependencies loaded from |
This is not an aliasify issue, but a browserify one. A transform is only applied to source files, not node_modules (I had the same problem, and found this out via browserify/browserify#501) |
Yes you seem to be correct. Whenever specifying the transform, we seem to need to set
Apologies for the confusion, I guess that's down to me being unclear as to how transforms work. There's a lot of the Browserify documents to digest! |
Seems to not work for me, I have: "browserify": {
"transform": [
["aliasify", {
"global": true,
"debug": true,
"aliases": {
"react": "preact-compat",
"react-dom": "preact-compat"
}
}]
]
}, and still get plenty of:
I tried adding the package.json config as mentioned in the readme, but that seems to have no effect. Any suggestions? |
This might help with defining global transforms in the package.json: |
Breaks on |
I've been doing some testing on using aliasify to replace requires of underscore for lodash. I've enabled verbose to be true. I've ran into an issue where in Backbone it still requires underscore instead of lodash.
See the output below:
Output:
Configuration:
The text was updated successfully, but these errors were encountered: