Skip to content

# in file path to project causes error during build/serve #7071

Description

@Jesse-longname

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.

  1. Create folder with a '#' in the name. (eg. '#project' or 'te#st')
  2. ng new project
  3. cd project
  4. npm install
  5. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgenthelp wantedLabel noting an issue which the team is looking for contribution from the community to fixseverity2: inconvenienttype: bug/fix

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions