You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It seems to me that you're either using webpack to build your javascript, or you're not, and if you are, then it's really rare that you don't want to use the --bundle option. It's annoying to have to never forget to add this to every single command.
Describe the solution you'd like
Some way to set in nsconfig.json settings that --bundle is the default and to provide a --no-bundle option in the event that you don't want to bundle with webpack.
We've already implemented such functionality in the NativeScript CLI. All you need is to install the next version of NativeScript CLI - npm i -g nativescript@next and add the following in your nsconfig.json file
{
"useLegacyWorkflow": false
}
This will enable hmr by default for your project for all commands.
Is your feature request related to a problem? Please describe.
It seems to me that you're either using webpack to build your javascript, or you're not, and if you are, then it's really rare that you don't want to use the
--bundle
option. It's annoying to have to never forget to add this to every single command.Describe the solution you'd like
Some way to set in
nsconfig.json
settings that--bundle
is the default and to provide a--no-bundle
option in the event that you don't want to bundle with webpack.Describe alternatives you've considered
Right now, we work around this by having:
To wrap every native script command that you might want to use in order to ensure that the
--bundle
flag is set.The text was updated successfully, but these errors were encountered: