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

Module creation fails #2668

Closed
JohnCashmore opened this issue Oct 12, 2016 · 3 comments
Closed

Module creation fails #2668

JohnCashmore opened this issue Oct 12, 2016 · 3 comments
Assignees
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful type: bug/fix

Comments

@JohnCashmore
Copy link
Contributor

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Ubuntu 16

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

angular-cli: 1.0.0-beta.17
node: 4.6.0
os: linux x64

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

When creating a new module the name is auto changed for the create but it appears not for the rest.

The log given by the failure.

Normally this include a stack trace and some more information.

➜ my-app git:(master) ✗ ng g module rulesManagement
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
installing module
create src/app/rules-management/rules-management.module.ts
installing component
Invalid path: "/home/developer/Projects/my-app/src/app/rulesManagement"" is not a valid path.
➜ my-app git:(master) ✗

@filipesilva
Copy link
Contributor

@Brocco can you have a look?

@filipesilva filipesilva added type: bug/fix command: generate P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful labels Oct 14, 2016
@Brocco
Copy link
Contributor

Brocco commented Oct 18, 2016

This will be resolved by PR #2756 and is a dupe of issue #2724, this issue can be tracked there

@Brocco Brocco closed this as completed Oct 18, 2016
@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 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful type: bug/fix
Projects
None yet
Development

No branches or pull requests

3 participants