Skip to content
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

Closed
jdanyow opened this issue Sep 9, 2016 · 11 comments
Closed

unable to rename node module #309

jdanyow opened this issue Sep 9, 2016 · 11 comments

Comments

@jdanyow
Copy link
Contributor

jdanyow commented Sep 9, 2016

aurelia/animator-velocity#13

Renaming the npm package "velocity-animate" to "velocity" breaks the build.

@EisenbergEffect
Copy link
Contributor

@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.

@jdanyow
Copy link
Contributor Author

jdanyow commented Sep 30, 2016

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)

@EisenbergEffect
Copy link
Contributor

The latest CLI is 0.20.1 Can you try that?

On Sep 30, 2016 2:25 AM, "Jeremy Danyow" [email protected] wrote:

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)
aurelia/animator-velocity#13 (comment)


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#309 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAIBna1ZmtJqNUF_HpAAC8dt17cdaKYyks5qvNWMgaJpZM4J4otT
.

@DarienFord
Copy link

This is still broken.

@simonfox
Copy link
Contributor

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?

cc @EisenbergEffect

@EisenbergEffect
Copy link
Contributor

@JeroenVinke is the best person to provide guidance on this issue.

@JeroenVinke
Copy link
Collaborator

Now that I think of it, #589 will allow us to alias modules because it enables the use of the map property in the requirejs config:

"map": {
    "*": {
      "my-renamed-package": "my-package"
    }
  },

@jpravetz
Copy link

jpravetz commented Dec 22, 2017

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.

@zewa666
Copy link
Member

zewa666 commented Oct 8, 2018

@huochunpeng this should be resolved with the new auto-tracer right?

@3cp
Copy link
Member

3cp commented Oct 8, 2018

Yes, it should be fixed by new tracer. BTW, requirejs config map is not supported anymore, because new tracer doesn't use requirejs runtime to help tracing.

@zewa666 zewa666 closed this as completed Oct 8, 2018
@3cp
Copy link
Member

3cp commented Oct 8, 2018

I have to point out while rename generally works, it is not enough for this velocity case.

aurelia-animator-velocity requires velocity-animator/velocity.ui, then velocity-animator/velocity.ui requires velocity (resulting to search npm package velocity) instead of ./velocity.

Both velocity-animate and velocity has to point to the same package. So aurelia/animator-velocity#13 (comment) is the only working workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants