You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
# in file path to project causes error during build/serve #7071
Create folder with a '#' in the name. (eg. '#project' or 'te#st')
ng new project
cd project
npm install
ng build (or ng serve)
The log given by the failure.
You an error similar to the following:
ERROR in Could not resolve "C:/JesseDev/Te" from "C:/JesseDev/Te".
Desired functionality.
Accept the use of '#' in folder names leading to the project.
Mention any other details that might be useful.
I spent a good half day trying to figure this out. Sure, better naming conventions could have prevented this, but I would still consider it a bug. A better error message would have been appreciated (invalid folder structure maybe?)
Also, if you use the --watch flag on build or serve, then trigger a rebuild, it works fine.
Activity
angular-automatic-lock-bot commentedon Sep 7, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.