-
-
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
animator-velocity build errors #277
Comments
Is |
Excerpt from the package file:
I set up a similar project and am getting the same errors (just to confirm with @aidesigner).
Add this line to the
Could be some tracing strangeness? |
I first posted this question on Aurelia-Velocity before believing in to be a CLI issue. aurelia/animator-velocity#13 presented a good analysis (jdanyow), which lead me to insert the code below in my aurelia.json. Everything works, but the browser debug console always starts with the error message "Uncaught Error: Mismatched anonymous define() module: function () {" followed by entire content of velocity.ui.js. It would be nice to have this message go away. auelia.json snippet: |
Have you tried the latest version of the CLI? I thought we had fixed the anonymous define issue. |
Running CLI 0.17.0, and I am having trouble updating the CLI. It appears each au cli project has aurelia-cli locally installed. Therefore under package.json I change aurelia-cli:"^0.17.0" to "^0.20.0" and ran "npm install aurelia-cli". Now my usual "au run" says invalid command "run", so I had to revert back to 0.17.0. Do I have to set up a new au cli project whenever the CLI is updated? Also running global aurelia-cli install again seems problematic: $ npm install aurelia-cli -g |
No. You probably have some sort of cache issue. I think there are issues with npm on windows related to npm cache. |
Very well I will work on clearing the cache and see if originally problem is fixed. However I am missing the big picture. Should aurelia-cli be installed globally and locally (ie. "aurelia-cli": "^0.17.0" in package.json)? |
Yes but the global only defers to the local once the project is created. On Oct 6, 2016 9:19 PM, "aidesigner" [email protected] wrote:
|
The latest CLI corrected the anonymous define issue. To get rid of the npm aurelia-cli update issue I had to change pakage.json from "^0.20.0" to "^0.19.0", and 20.2 was still installed (Strange). Clearing the cache did not help. The ticket issue is now solved by following the aurelia/animator-velocity#13 workaround. Removing the workaround is being tracked at #309. |
I'm submitting a bug report
Library Version: 0.17.0
Operating System: Windows 10
Node Version: 6.2.0
NPM Version: 3.8.9
Browser: Chrome
Language: TypeScript
Current behavior:
As I migrated my project from Aurelia JSPM to the CLI I can no longer get built in library Aurelia Velocity working. I first opened an issue (aurelia/animator-velocity#13) in animator-velocity, but I believe the CLI may be the problem. Also this may be indicative of the issues that arises when adding stubborn libraries. Below is the exact sequence, from scratch, that produces error (Also below). Aurelia with Velocity animations is really awesome, but cannot get the CLI to play nice.
Create Aurelia CLI project and then execute bash commands:
au new - Custom/Typescript/Sass/No Test/VSCode
npm install aurelia-animator-velocity --save
typings install dt~velocity-animate --save --global
Add dependencies into aurelia.json:
"velocity-animate",
{
"name": "aurelia-animator-velocity",
"path": "../node_modules/aurelia-animator-velocity/dist/amd",
"main": "aurelia-animator-velocity"
}
Comment out below in aurelia-animator-velocity.d.ts (Separate Issue):
//import velocity from 'velocity-animate';
Add simple import to app.ts to test aurelia-animator-velocity:
import {VelocityAnimator} from "aurelia-animator-velocity";
Running "au build" produces error below. The current issue is the path to velocity.ui.js should not contains src. Not sure if this a CLI issue or a velocity.ui.js path issue within animator-velocity.
The text was updated successfully, but these errors were encountered: