Bug Report or Feature Request (mark with an x)
- [x ] bug report -> please search issues before submitting
- [ ] feature request
Versions.
@angular/cli: 1.2.1
node: 6.11.0
os: win32 x64
@angular/animations: 4.3.1
@angular/common: 4.3.1
@angular/compiler: 4.3.1
@angular/core: 4.3.1
@angular/forms: 4.3.1
@angular/http: 4.3.1
@angular/platform-browser: 4.3.1
@angular/platform-browser-dynamic: 4.3.1
@angular/router: 4.3.1
@angular/cli: 1.2.1
@angular/compiler-cli: 4.3.1
Repro steps.
- 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.
Bug Report or Feature Request (mark with an
x)Versions.
@angular/cli: 1.2.1
node: 6.11.0
os: win32 x64
@angular/animations: 4.3.1
@angular/common: 4.3.1
@angular/compiler: 4.3.1
@angular/core: 4.3.1
@angular/forms: 4.3.1
@angular/http: 4.3.1
@angular/platform-browser: 4.3.1
@angular/platform-browser-dynamic: 4.3.1
@angular/router: 4.3.1
@angular/cli: 1.2.1
@angular/compiler-cli: 4.3.1
Repro steps.
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.