Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

Why are the path prefix needed with NG CLI? #23

Closed
Vad1mo opened this issue Dec 28, 2016 · 1 comment
Closed

Why are the path prefix needed with NG CLI? #23

Vad1mo opened this issue Dec 28, 2016 · 1 comment
Assignees

Comments

@Vad1mo
Copy link

Vad1mo commented Dec 28, 2016

Is not very clear to me why do the references in @Components need since 0.8.0 the local path prefix ./ like in in templateUrl: './app.component.html'. As I see it it only affects the NG CLI Branch.

Changes in this commit
ef655e8

or this pull request:
#17

@Shijir
Copy link
Contributor

Shijir commented Jan 4, 2017

Yes, Angular-CLI used to work fine with specifying just file names in the style or templateUrls properties. But one of their recent changes introduced the following error: Module not found: ... if you don't prepend ./. I think they are fixing the issue in angular/angular-cli#3838 so it will be more flexible meaning you can use both the old and new ways of specifying the component-relative files. For example, both of them will be allowed templateUrl: './app.component.html' and templateUrl: 'app.component.html'

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants