-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
remove-package tool doesn't work off current plugin-seed #8
Comments
Looks like #7 tries to address the issue, however I think checking for existence covers a wider range of possibilities |
@pekevski thanks for ping on this. I’m going to work on getting updates out by tomorrow afternoon on this. |
Actually @pekevski i like your suggested fix better if you want to PR that? If you don’t have time no worries - I may revert the other tomorrow as I think your suggestion would cover more and be simpler. |
Sure ill quickly do it now for you |
Only delete the specific package from demo flavours used rather than depend on a package.json being present. Closes: NativeScript#8
Only delete the specific package from demo flavours used rather than depend on a package.json being present. Closes: #8
Looks like the plugin seed only has demos for plain/ts and angular apps in the
/apps
directory. So when a developernpm run add
's a plugin it will only get added / removed from the following directories:Looks like the remove-package code loops through all flavours of demo without actually checking they exist in the file tree.
Would the appropriate fix be to
/app
with a package.json; orto
packages/plugin-tools/src/generators/remove-package/index.ts
?(Happy to make the fix based on the best way forward as well)
The text was updated successfully, but these errors were encountered: