-
-
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
au new --here fails to scaffold project #1188
Comments
It looks like win32 rewrote cli/lib/commands/new/command.js Line 7 in 02365f8
It's probably the behaviour of spawn in child_process. I will run some tests. |
In the meanwhile, you can directly do |
I'm afraid that doesn't work either, the forward-slash is swapped for out for a backslash
full log:
You can see it recognises the forward-slash up until and including line 30 but line 36 shows it's flipped it. Tried this with Powershell, VSCode Terminal (also Powershell but why not?) and cmd.exe, all the same Pretty sure I tried this before logging the issue but I wanted to confirm. |
Thanks very much for the investigation! I have not got a windows machine to try yet.
Probably node/npm/npx rewrote the arguments? |
Pls try au new again. |
au new worked after I installed the upgraded makes package. Thanks. |
You don't need to install makes. Npx makes (which au new simply wraps) works with zero installation. This is a feature of npx, it fetches from latest npm package if you didn't install it. |
With zero install, npx makes always uses latest makes version. It doesn't keep makes in your npm global installed packages. |
TL;DR; I must have been doing something wrong then as simply running au new didn't do the job. I still have the console output:
|
Sounds like you have a trapped local makes v2.0.1 somewhere. Then in the folder where it didn't work, use
That will tell you where the "makes" is installed. I am guessing somewhere in a |
I've removed the makes package and tried to identify the 'trapped' makes package but it's doesn't appear to be there...
...and npx reports it's still using version 2.0.1...
🤷♂️ |
I have no idea why and where it kept the old v2.0.1, my Maybe try resetting all npm caches Do you use or your company use an internal npm server like https://verdaccio.org? |
It looks like your makes is not fetched from remote
My log shows extra line
|
Nope, this is personal dev stuff, no company shenanigans. I ran Cleared my npm cache as you suggested but |
Just noticed you are on npm 7 with node 15. That might be the cause. I will try that version. |
Yes, npx in npm 7 definitely changed behaviour, it now install the package somewhere. The somewhere must be the hidden cache in your case.
|
From the linked npm issue, the cached location for your local npx commands is your local You can clean up the folder to force npx to download the latest version. |
npm v7.5.2 is released with fix of the npx ignoring latest version. |
I'm submitting a bug report
2.0.2
Please tell us about your environment:
Operating System:
Windows 10
Node Version:
15.0.1
NPM Version:
7.0.3
Browser:
n/a
Language:
n/a
Loader/bundler:
n/a
Current behavior:
calling au new ( or npx makes aurelia/v1) returns an error:
Command completes without error
The text was updated successfully, but these errors were encountered: