-
-
Notifications
You must be signed in to change notification settings - Fork 197
After upgraded to nativescript 3.1.2, tns run android still works. But npm run start-android-bundle get error #2962
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
Comments
Hi @xgu01, Can you please add android platform before
|
following the exact steps above I am given the same error as OP. Brand new project and I ran everything in the order you said. |
Hi @SamuelGRwebfab It looks to be NativeScript/nativescript-dev-webpack#214 Can you downgrade to If that is the case, it will be resolved later today or tomorrow with |
I downgraded to 0.7.0. it works again. Thanks
From: dtopuzov [mailto:[email protected]]
Sent: Wednesday, July 12, 2017 7:03 AM
To: NativeScript/nativescript-cli <[email protected]>
Cc: Xianzhang Gu <[email protected]>; Mention <[email protected]>
Subject: Re: [NativeScript/nativescript-cli] After upgraded to nativescript 3.1.2, tns run android still works. But npm run start-android-bundle get error (#2962)
Hi @SamuelGRwebfab<https://github.com/samuelgrwebfab>
It looks to be
NativeScript/nativescript-dev-webpack#214<NativeScript/nativescript-dev-webpack#214>
Can you downgrade to [email protected] and try again?
If that is the case, it will be resolved later today or tomorrow with [email protected].
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#2962 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AckfMK1s1CwIxR86dM6ZckzpYYFWyTeYks5sNNIhgaJpZM4OReXj>.
This email and any attachments may contain legal privileged, confidential, law enforcement sensitive, or trade secret information. Access to this e-mail or it’s attachments by anyone other than the intended recipient(s) is unauthorized. If you are not the intended recipient (or responsible for delivery of the message to such person), you may not use, copy, forward, distribute or deliver to anyone this message (or any part of its contents ) or take any action in reliance on it. In such case, you should destroy this message, and notify us immediately. If you have received this email in error, please notify us immediately by e-mail or telephone and delete the e-mail from any computer. The views, opinions, conclusions and other information expressed in this electronic mail are not given or endorsed by the company unless otherwise indicated by an authorized representative independent of this message.
|
I figured it out, i needed to downgrade to 0.7.0 to resolve all of my issues. |
@SamuelGRwebfab @xgu01 |
Did you verify this is a real problem by searching Stack Overflow and the other open issues in this repo?
Yes
Tell us about the problem
After upgraded to nativescript 3.1.2, tns run android still works. But npm run start-android-bundle get error
Which platform(s) does your issue occur on?
Android
Please provide the following version numbers that your issue occurs with:
3.1.0
"tns-android"
and"tns-ios"
properties in the3.1.1
package.json
file of yourproject)
Please tell us how to recreate the issue in as much detail as possible.
tns create ng1 --ng
npm install --save-dev nativescript-dev-webpack
npm install
npm run start-android-bundle
error message:
C:\SVN\dev\test\ng1>npm run start-android-bundle
Running tns prepare...
module.js:471
throw err;
^
Error: Cannot find module 'C:\SVN\dev\test\ng1\node_modules\nativescript\bin\tns
'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3
child process exited with code 1
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\xgu\AppData\Ro
aming\npm\node_modules\npm\bin\npm-cli.js" "run" "ns-bundle" "--android" "-
-run-app"
npm ERR! node v6.9.5
npm ERR! npm v4.1.2
npm ERR! code ELIFECYCLE
npm ERR! @ ns-bundle:
ns-bundle
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ ns-bundle script 'ns-bundle'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! ns-bundle
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\SVN\dev\test\ng1\npm-debug.log
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\xgu\AppData\Ro
aming\npm\node_modules\npm\bin\npm-cli.js" "run" "start-android-bundle"
npm ERR! node v6.9.5
npm ERR! npm v4.1.2
npm ERR! code ELIFECYCLE
npm ERR! @ start-android-bundle:
npm run ns-bundle --android --run-app
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ start-android-bundle script 'npm run ns-bundle --androi
d --run-app'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! npm run ns-bundle --android --run-app
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\SVN\dev\test\ng1\npm-debug.log
Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.
The text was updated successfully, but these errors were encountered: