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

ace --version fails with a Syntax Error on some setups #45

Closed
rdeltour opened this issue Oct 4, 2017 · 3 comments
Closed

ace --version fails with a Syntax Error on some setups #45

rdeltour opened this issue Oct 4, 2017 · 3 comments
Assignees
Labels
Milestone

Comments

@rdeltour
Copy link
Member

rdeltour commented Oct 4, 2017

Reported by Nick Williamson:

ace --version

produced (with the directory path before npm replaced by an ellipsis)

...\npm\node_modules\ace-core\dist\report\repor```
t-builders.js:89
 ) {
 ^
SyntaxError: Unexpected token )
  at createScript (vm.js:56:10)
  at Object.runInThisContext (vm.js:97:10)
  at Module._compile (module.js:542:28)
  at Object.Module._extensions..js (module.js:579:10)
  at Module.load (module.js:487:32)
  at tryModuleLoad (module.js:446:12)
  at Function.Module._load (module.js:438:3)
  at Module.require (module.js:497:17)
  at require (internal/module.js:20:19)
...\npm\node_modules
\ace-core\dist\report\axe2ace.js:5:18)
@rdeltour rdeltour added the bug label Oct 4, 2017
@rdeltour rdeltour added this to the Beta 1 milestone Oct 4, 2017
@rdeltour rdeltour self-assigned this Oct 4, 2017
@mattgarrish
Copy link

I wasn't able to update, either.

When I run "npm update ace-core -g" a progress bar for node 6.11.0 appears briefly and then I'm returned to the command prompt without any messages. If I run ace --version I'm still on 0.2.0

I just tried a delete and re-install and now I'm getting the same error as Nick.

I had to uninstall everything, get node 8.6.0 and reinstall to make things work. This is on Win10.

@rdeltour
Copy link
Member Author

rdeltour commented Oct 4, 2017

I logged the update issue as #46, it seems to be a problem with npm.
The Node compatibility issue is tracked as #47.

@clapierre
Copy link

clapierre commented Oct 6, 2017 via email

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

No branches or pull requests

3 participants