Skip to content

Conversation

@NathanWalker
Copy link

  • Seed was currently broken due to usage of ^ on typescript dep which was installing 2.4 which causes problems
  • While fixing the above I went ahead and bumped the deps to latest
  • A new command npm run nuke was added to help users clear plugin and demo files for a fresh install when needed

src/package.json Outdated
"type": "git",
"url": "https://github.com/YourName/nativescript-yourplugin.git"
"demo.android": "npm i && npm run tsc && cd ../demo && tns run android --syncAllFiles",
"nuke": "rm -rf node_modules && cd ../demo && rm -rf hooks node_modules platforms"
Copy link

@radeva radeva Jul 10, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would mind to rename the command from "nuke" to "clean" or "clear"? I think it would be more meaningful for users. What's your opinion?

In addition, you can run npm run plugin.link in the nuke command so that the plugin is linked again in the demo after node_modules are deleted.

src/package.json Outdated
"platforms": {
"android": "3.0.0",
"ios": "3.0.0"
"android": "3.1.1",
Copy link

@radeva radeva Jul 10, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general this is the minimum required version of the runtime that will be able to process the plugin in the application. This means that setting runtime version to 3.1.1 here will make the plugin incompatible with 3.0 apps which shouldn't be a problem. That's why we prefer to have 3.0.0 here.

@NathanWalker
Copy link
Author

@radeva makes perfect sense! Updated now 👍

@radeva radeva merged commit d26dc63 into NativeScript:master Jul 12, 2017
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

Successfully merging this pull request may close these issues.

2 participants