Introduce command (tns migrate
) to migrate old project to 6.0.0 requirements
#4646
Labels
Milestone
Is your feature request related to a problem? Please describe.
In 6.0.0 release, we'll have new requirements for applications build process, i.e. all apps must have webpack as dependencies, several development plugins should be replaced with others, etc.
All of these changes could take a lot of time to the users and several issues might occur during the process. So it will be great in case
tns update
command can handle all these changes.Describe the solution you'd like
The
tns update
command should update the following components of the application:tns-core-modules
andtns-core-modules-widgets
versionsnativescript-dev-webpack
versionwebpack.config.js
file according to latest changes - create a backup of the old onehooks
directory - create backup of it and allownpm
to recreate it on its ownnativescript-dev-sass
should be replaced withnode-sass
nativescript-dev-typescript
should be replaced withtypescript
(possiblytypescript
is already a devDependency of the project)nativescript-dev-less
should be replaced withless
After updating the package.json and backing up the directories, CLI should execute
npm rebuild
, so all new dependencies and devDependencies will be installed and all required hooks will be generated in the project.Also it will be great to check the project files and notify the users if there are
.xml
/.css
files that do not follow the convention requirements of our webpack logic (i.e. they do not havepage
orroot
in the name) and show warnings for them.Describe alternatives you've considered
CLI might show interactive prompts which of the mentioned components to be updated.
The text was updated successfully, but these errors were encountered: