@quasar/app-webpack-v4.0.0-beta.20

#quasar

Fixes

• fix(app-webpack): Capacitor/Cordova on Windows host -> Android Studio not being launched when running "quasar build -m capacitor -T android --ide" #17420
• fix(app-webpack): fix types feature flags (#17429)

Important: After upgrading

The feature flag files must be deleted from your project folder. They need to be generated again (will happen automatically).

Using rimraf through npx(or pnpx, yarn dlx, bunx)

$ npx rimraf -g ./**/*-flag.d.ts
$ quasar build # or dev

Unix-like (Linux, macOS):

$ rm ./**/*-flag.d.ts
$ quasar build # or dev

Windows (CMD):

> del /s *-flag.d.ts
> quasar build &:: or dev

Windows (PowerShell):

> Remove-Item -Recurse -Filter *-flag.d.ts
> quasar build # or dev

#17301 changes moduleResolution from node to bundler. That broke the feature flags system. Here is an example common error:

Property store does not exist on type BootFileParams

It's because even though TS normally doesn't enforce the file extension inside the app code and imports from node_modules when using bundler, it does enforce it for wildcard package.json > exports entries. So, quasar/dist/types/feature-flag no longer works and must be changed to quasar/dist/types/feature-flag.d.ts instead.

This change will only apply to feature flags generated after the release of this. So, existing projects will only benefit from it when they add Pinia or build modes, OR delete the feature flag files and run quasar dev/quasar build to re-generate them. New projects will work fine.

Donations

Quasar Framework is an open-source MIT-licensed project made possible due to the generous contributions by sponsors and backers. If you are interested in supporting this project, please consider the following:

• Becoming a sponsor on Github
• One-off donation via PayPal

Generated by RSStT. The copyright belongs to the original author.

Source