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

ng g migrate-module --name=<module-name> stops at opening the module file. #2009

Closed
AnandkumarBShetty opened this issue Oct 10, 2019 · 1 comment

Comments

@AnandkumarBShetty
Copy link

AnandkumarBShetty commented Oct 10, 2019

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):
√ Getting NativeScript components versions information...
√ Component nativescript has 6.1.2 version and is up to date.
√ Component tns-core-modules has 6.1.1 version and is up to date.
‼ Update available for component tns-android. Your current version is 6.1.1 and the latest available version is 6.1.2.
× Component tns-ios is not installed.

Angular CLI: 8.3.8
Node: 10.16.0
OS: win32 x64
Angular: 8.2.9
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package Version

@angular-devkit/architect 0.802.2
@angular-devkit/build-angular 0.802.2
@angular-devkit/build-optimizer 0.802.2
@angular-devkit/build-webpack 0.802.2
@angular-devkit/core 8.2.2
@angular-devkit/schematics 8.2.2
@angular/cli 8.3.8
@angular/http 7.2.15
@ngtools/webpack 8.2.2
@schematics/angular 8.3.8
@schematics/update 0.803.8
rxjs 6.5.3
typescript 3.5.3
webpack 4.38.0

Describe the bug
ng g migrate-module --name= stops at opening the module file while it is expected to create the module.tns file and create /update the components within that module. Had to use CTRL+C key to exit out.

To Reproduce
ng g migrate-module --name=

Expected behavior
create the module.tns (this is other than the app module) file and create /update the components within that module.

Additional context
Raised a documentation bug for the order of sequence of steps for migration.
https://github.com/NativeScript/docs/issues/1812

@AnandkumarBShetty
Copy link
Author

Closing this issue as the issue is not seen with the latest version of NativeScript.
ng g migrate-module --name= works fine now. The order of migration steps need to change as provided in the nativescripts/docs for migrating existing project.
Though it stops for some time (few minutes) at file contents of the non -app module . It did complete in quick time.

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

No branches or pull requests

1 participant