Skip to content

[3.0.0] Can't remove or update plugins #2792

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

Closed
3rror404 opened this issue May 9, 2017 · 6 comments
Closed

[3.0.0] Can't remove or update plugins #2792

3rror404 opened this issue May 9, 2017 · 6 comments

Comments

@3rror404
Copy link

3rror404 commented May 9, 2017

I have just updated to N 3.0.0 following the instructions here and I'm now unable to remove or update any plugins.

tns plugin update nativescript-background-http
SyntaxError: Expected "/*", "//" or "{" but "<" found.
tns plugin remove nativescript-background-http
Plugin "nativescript-background-http" is not installed.

tns plugin remove tns plugin remove nativescript-geolocation
SyntaxError: Expected "/*", "//" or "{" but "<" found.

This syntax error looks very similar to another issue I reported a few days ago: #2782 (comment)

┌──────────────────┬─────────────────┬────────────────┬───────────────┐
│ Component        │ Current version │ Latest version │ Information   │
│ nativescript     │ 3.0.0           │ 3.0.0          │ Up to date    │
│ tns-core-modules │ 3.0.0           │ 3.0.0          │ Up to date    │
│ tns-android      │                 │ 3.0.0          │ Not installed │
│ tns-ios          │ 3.0.0           │ 3.0.0          │ Up to date    │
└──────────────────┴─────────────────┴────────────────┴───────────────┘

Dependencies:
┌────────────────────────────────┬─────────┐
│ Plugin                         │ Version │
│ nativescript-background-http   │ ^2.5.1  │
│ nativescript-carousel          │ ^2.3.1  │
│ nativescript-geolocation       │ 0.0.19  │
│ nativescript-google-maps-sdk   │ ^2.0.3  │
│ nativescript-imagepicker       │ ^2.5.1  │
│ nativescript-iqkeyboardmanager │ ^1.0.1  │
│ nativescript-permissions       │ ^1.2.3  │
│ nativescript-theme-core        │ ~1.0.2  │
│ tns-core-modules               │ ^3.0.0  │
└────────────────────────────────┴─────────┘
Dev Dependencies:
┌───────────────────────────────────┬─────────┐
│ Plugin                            │ Version │
│ babel-traverse                    │ 6.23.1  │
│ babel-types                       │ 6.23.0  │
│ babylon                           │ 6.16.1  │
│ lazy                              │ 1.0.11  │
│ nativescript-dev-android-snapshot │ ^0.*.*  │
└───────────────────────────────────┴─────────┘
@3rror404
Copy link
Author

3rror404 commented May 9, 2017

It seems that the plugin is actually removed when running tns plugin remove <plugin_name> even though there is an error displayed in terminal.

@dtopuzov dtopuzov added the bug label May 9, 2017
@dtopuzov dtopuzov added this to the 3.1.0 milestone May 9, 2017
@dtopuzov
Copy link
Contributor

dtopuzov commented May 9, 2017

Hi @3rror404 can you run tns plugin update <some-plugin> --log trace and paste the output.
Can you also post full package.json of your app, since I'm not able to reproduce the issue with single plugin.

Can you also try to remove following from your package.json:

babel-traverse
babel-types
babylon
lazy  

and try plugin update again?

It will be also useful to know what is your node/npm version.

Workaround:
Use npm i <plugin-name> --save for regular plugins and npm i <plugin-name> --save-dev for dev plugins like nativescript-dev-android-snapshot

@3rror404
Copy link
Author

3rror404 commented May 10, 2017

Hi @dtopuzov,

I had to downgrade to N 2.5.4 to continue my project due to critical bugs (such as NativeScript/NativeScript#4141) so I'm unable to provide any more information currently.

If I get the time I will try to update again and do as you have requested.

@pkoleva pkoleva removed this from the 3.1.0 milestone Jun 6, 2017
@dtopuzov
Copy link
Contributor

Hi @3rror404

Did you managed to re-test the issue with 3.* versions?
NativeScript/NativeScript#4141 is already fixed in [email protected].

@3rror404
Copy link
Author

Hi @dtopuzov,

I haven't updated this specific project to N3 yet, but I haven't experienced it in other N3.x based projects so maybe it was just an issue with 3.0.0?

@dtopuzov
Copy link
Contributor

We where never able to reproduce it, so I expect it is environment issue.
May be it happens with specific versions of node and npm.

Closing the issue since it is not longer reproducible.

@3rror404 let us know if you encounter it again.

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

No branches or pull requests

3 participants