Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@angular-cli 1.1.0 rc.1 not support baseUrl import ? #6451

Closed
Feng-JY opened this issue May 25, 2017 · 4 comments · Fixed by #6463
Closed

@angular-cli 1.1.0 rc.1 not support baseUrl import ? #6451

Feng-JY opened this issue May 25, 2017 · 4 comments · Fixed by #6463

Comments

@Feng-JY
Copy link

Feng-JY commented May 25, 2017

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request

Versions.

@angular/cli: 1.1.0-rc.1
node: 6.10.2
os: darwin x64
@angular/animations: 4.1.3
@angular/common: 4.1.3
@angular/compiler: 4.1.3
@angular/core: 4.1.3
@angular/forms: 4.1.3
@angular/http: 4.1.3
@angular/platform-browser: 4.1.3
@angular/platform-browser-dynamic: 4.1.3
@angular/router: 4.1.3
@angular/cli: 1.1.0-rc.1
@angular/compiler-cli: 4.1.3
@angular/language-service: 4.1.3

Repro steps.

ng new angular-new-cli
yarn install
new until.ts in app/
this is until.ts content export const TEST = 'test';
in app.component.ts import { TEST } from 'app/until';

The log given by the failure.

ERROR in ./src/app/app.component.ts
Module not found: Error: Can't resolve 'app/until' in '/Users/feng/ng/angular-new-cli/src/app'
@ ./src/app/app.component.ts 8:0-33
@ ./src/app/app.module.ts
@ ./src/main.ts
@ multi webpack-dev-server/client?http://localhost:4200 ./src/main.ts

Desired functionality.

@angular-cli 1.1.0 rc.0 -> 1.1.0 rc.1 not support baseUrl import ?
if have multi-level directory
how to do more elegant

Mention any other details that might be useful.

@Simon-Briggs
Copy link

Simon-Briggs commented May 25, 2017

I'm getting the same error having just upgraded to @angular-cli 1.0.5

1.0.4 is working fine.

Something here?
0f24e04#diff-75e7bcb889f70652f52a155809ca0c37R89

@wtospit
Copy link

wtospit commented May 25, 2017

I have got this issue as well in my project, but it's look strange that, when I tried to reproduce this issue by creating new project, it doesn't show any error, and went well....

I'm using version 1.0.5

@hansl
Copy link
Contributor

hansl commented May 25, 2017

Seems like it is a regression on 1.0.4. I'll revert and do a re-release right away.

@hansl hansl self-assigned this May 25, 2017
hansl added a commit to hansl/angular-cli that referenced this issue May 25, 2017
hansl added a commit that referenced this issue May 25, 2017
hansl added a commit that referenced this issue May 25, 2017
hansl added a commit that referenced this issue May 25, 2017
hansl added a commit to hansl/angular-cli that referenced this issue Aug 2, 2017
This is a similar version of angular#5033. Reverted in angular#6463 because of issue angular#6451.
hansl added a commit to hansl/angular-cli that referenced this issue Aug 2, 2017
This is a similar version of angular#5033. Reverted in angular#6463 because of issue angular#6451.
hansl added a commit to hansl/angular-cli that referenced this issue Aug 2, 2017
This is a similar version of angular#5033. Reverted in angular#6463 because of issue angular#6451.
hansl added a commit to hansl/angular-cli that referenced this issue Aug 2, 2017
This is a similar version of angular#5033. Reverted in angular#6463 because of issue angular#6451.
hansl added a commit to hansl/angular-cli that referenced this issue Aug 2, 2017
This is a similar version of angular#5033. Reverted in angular#6463 because of issue angular#6451.
hansl added a commit to hansl/angular-cli that referenced this issue Aug 2, 2017
This is a similar version of angular#5033. Reverted in angular#6463 because of issue angular#6451.
hansl added a commit to hansl/angular-cli that referenced this issue Aug 2, 2017
This is a similar version of angular#5033. Reverted in angular#6463 because of issue angular#6451.

This is a feature because we do not want it in 1.3.0
hansl added a commit to hansl/angular-cli that referenced this issue Aug 3, 2017
This is a similar version of angular#5033. Reverted in angular#6463 because of issue angular#6451.

This is a feature because we do not want it in 1.3.0
hansl added a commit to hansl/angular-cli that referenced this issue Aug 3, 2017
This is a similar version of angular#5033. Reverted in angular#6463 because of issue angular#6451.

This is a feature because we do not want it in 1.3.0
hansl added a commit that referenced this issue Aug 9, 2017
This is a similar version of #5033. Reverted in #6463 because of issue #6451.

This is a feature because we do not want it in 1.3.0
hansl added a commit that referenced this issue Aug 9, 2017
This is a similar version of #5033. Reverted in #6463 because of issue #6451.

This is a feature because we do not want it in 1.3.0
dond2clouds pushed a commit to d2clouds/speedray-cli that referenced this issue Apr 23, 2018
dond2clouds pushed a commit to d2clouds/speedray-cli that referenced this issue Apr 23, 2018
This is a similar version of angular#5033. Reverted in angular#6463 because of issue angular#6451.

This is a feature because we do not want it in 1.3.0
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants