Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
While using the paths object inside tsconfig.json, module resolution doesn't seem to work anymore since the latest release. It did work on 1.3.0-rc.5. Ahead of Time does work. This seems to happen when you reference the src folder or anything lower down the tree
Versions.
@angular/cli: 1.3.0
node: 8.2.1
os: win32 x64
@angular/animations: 4.3.3
@angular/common: 4.3.3
@angular/compiler: 4.3.3
@angular/core: 4.3.3
@angular/forms: 4.3.3
@angular/http: 4.3.3
@angular/platform-browser: 4.3.3
@angular/platform-browser-dynamic: 4.3.3
@angular/router: 4.3.3
@angular/cli: 1.3.0
@angular/compiler-cli: 4.3.3
@angular/language-service: 4.3.3
Repro steps.
- Upgrade cli to version
1.3.0, this used to work in 1.3.0-rc.5 and before
- Create a project
- Set a paths property to
"@root/*": ["./*"] inside tsconfig.app..json
- Change the import of
AppComponent inside AppModule to import { AppComponent } from '@root/app/app.component';
- Run
ng serve
- Run
ng serve --aot to see that this does work
The log given by the failure.
ERROR in ./src/app/app.module.ts
Module not found: Error: Can't resolve '@root/app/app.component' in 'C:\Projects\angular-cli-v130-bug\src\app'
resolve '@root/app/app.component' in 'C:\Projects\angular-cli-v130-bug\src\app'
Parsed request is a module
using description file: C:\Projects\angular-cli-v130-bug\package.json (relative path: ./src/app)
Field 'browser' doesn't contain a valid alias configuration
after using description file: C:\Projects\angular-cli-v130-bug\package.json (relative path: ./src/app)
resolve as module
C:\Projects\angular-cli-v130-bug\src\app\node_modules doesn't exist or is not a directory
C:\Projects\angular-cli-v130-bug\src\node_modules doesn't exist or is not a directory
C:\Projects\node_modules doesn't exist or is not a directory
C:\node_modules doesn't exist or is not a directory
looking for modules in C:\Projects\angular-cli-v130-bug\node_modules
using description file: C:\Projects\angular-cli-v130-bug\package.json (relative path: ./node_modules)
Field 'browser' doesn't contain a valid alias configuration
after using description file: C:\Projects\angular-cli-v130-bug\package.json (relative path: ./node_modules)
using description file: C:\Projects\angular-cli-v130-bug\package.json (relative path: ./node_modules/@root/app/app.component)
no extension
Field 'browser' doesn't contain a valid alias configuration
C:\Projects\angular-cli-v130-bug\node_modules\@root\app\app.component doesn't exist
.ts
Field 'browser' doesn't contain a valid alias configuration
C:\Projects\angular-cli-v130-bug\node_modules\@root\app\app.component.ts doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
C:\Projects\angular-cli-v130-bug\node_modules\@root\app\app.component.js doesn't exist
as directory
C:\Projects\angular-cli-v130-bug\node_modules\@root\app\app.component doesn't exist
Desired functionality.
I would like to see no errors, obviously ;)
Mention any other details that might be useful.
Created a repo showing this issue
Bug Report or Feature Request (mark with an
x)While using the
pathsobject insidetsconfig.json, module resolution doesn't seem to work anymore since the latest release. It did work on1.3.0-rc.5. Ahead of Time does work. This seems to happen when you reference thesrcfolder or anything lower down the treeVersions.
@angular/cli: 1.3.0
node: 8.2.1
os: win32 x64
@angular/animations: 4.3.3
@angular/common: 4.3.3
@angular/compiler: 4.3.3
@angular/core: 4.3.3
@angular/forms: 4.3.3
@angular/http: 4.3.3
@angular/platform-browser: 4.3.3
@angular/platform-browser-dynamic: 4.3.3
@angular/router: 4.3.3
@angular/cli: 1.3.0
@angular/compiler-cli: 4.3.3
@angular/language-service: 4.3.3
Repro steps.
1.3.0, this used to work in1.3.0-rc.5and before"@root/*": ["./*"]insidetsconfig.app..jsonAppComponentinsideAppModuletoimport { AppComponent } from '@root/app/app.component';ng serveng serve --aotto see that this does workThe log given by the failure.
Desired functionality.
I would like to see no errors, obviously ;)
Mention any other details that might be useful.
Created a repo showing this issue