-
-
Notifications
You must be signed in to change notification settings - Fork 742
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
Issue creating a new project after changing NPM's folder routes #3404
Comments
This should be fixed via #3403 Running |
While the anterior problem has indeed disappeared (thank you!), alas it has a new complaint:
The folder indeed has been created, but it is empty. I'm assuming it's getting the "e:" part from the routes, which again are defined on
|
How fun 😞 I can only join the many other package maintainers in saying that upgrading to ES modules has been very unpleasant. Anyway. This should be fixed via #3405 and work in v5.0.20 or later. |
It is fixed indeed on my side, thank you for your work! |
Hello! So, for storage-related reasons I have my Node / NPM installation configured to store thing on the E: partition instead of C:, and while I haven't had any related troubles with other packages so far, it seems to have broken something when trying to create a new Feathers project:
Steps to reproduce
1 - Install NodeJs. Use the
npm config set --global
to change the prefix (toE:\Dev\nodeprefix
) and cache (toE:\Dev\nodecache
) routes of NPM.2- Try creating a new Feathers project with
npm create feathers@latest <name>
Expected behavior
Project is created successfully.
Actual behavior
After running
npm create feathers@latest <name>
, the console throws an error and stops:These are the contents of the log:
System configuration
Module versions (especially the part that's not working):
latest
version of Feathers.NodeJS version:
v20.11.0
Operating System:
Windows 11
The text was updated successfully, but these errors were encountered: