-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
unable to rename node module #309
Comments
@jdanyow Do you know what version of the CLI you had this issue with? I thought we enabled this at some point but I'm not sure. |
re-tested with 0.18.0, still seems to be an issue. To test: npm install aurelia-animator-velocity aurelia.json "aurelia-animator-velocity",
"jquery",
{
"name": "velocity",
"path": "../node_modules/velocity-animate",
"main": "velocity",
"deps": ["jquery"],
"resources": ["velocity.ui.js"]
} Workaround: aurelia/animator-velocity#13 (comment) |
The latest CLI is 0.20.1 Can you try that? On Sep 30, 2016 2:25 AM, "Jeremy Danyow" [email protected] wrote:
|
This is still broken. |
I am running into this just now (moving an app from JSPM to CLI). I would be happy to spend some time looking at it if somebody could give me some guidance? |
@JeroenVinke is the best person to provide guidance on this issue. |
Now that I think of it, #589 will allow us to alias modules because it enables the use of the
|
I was looking to see if, at this date, there was a less-kludgy way to include aurelia-animator-velocity when using the latest CLI. It looks like the module map suggestion #589 by @JeroenVinke has been put on hold, and so the shim workaround in #13 remains our only solution. Please correct me if I am wrong. |
@huochunpeng this should be resolved with the new auto-tracer right? |
Yes, it should be fixed by new tracer. BTW, requirejs config |
I have to point out while rename generally works, it is not enough for this velocity case.
Both |
aurelia/animator-velocity#13
Renaming the npm package "velocity-animate" to "velocity" breaks the build.
The text was updated successfully, but these errors were encountered: