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.
When using Quasar with webpack 5 you will get the following console warnings:
Should not import the named export 'version' (imported as 'version') from default-exporting module (only default export is available soon)
The reason for this warning is the named import from json, wich webpack will not support in the future:
node_modules/quasar/src/install.js
node_modules/quasar/src/vue-plugin.js
Describe the solution you'd like
These warnings are really annoying. It would be nice if quasar will support webpack 5. The implementation is quite simple. The json file has to be imported as default & the version has to be accessed directly.
Unfortunately, it's not easy to backport the fix to Quasar v1 also without introducing a breaking change (a required minimum version of q/app). But as things stand, Quasar v1 won't get Webpack 5 anyways (too many heavy breaking changes would be required overall). So closing because of being fixed in future Quasar v2.
Is your feature request related to a problem? Please describe.
When using Quasar with webpack 5 you will get the following console warnings:
Should not import the named export 'version' (imported as 'version') from default-exporting module (only default export is available soon)
The reason for this warning is the named import from json, wich webpack will not support in the future:
node_modules/quasar/src/install.js
node_modules/quasar/src/vue-plugin.js
Describe the solution you'd like
These warnings are really annoying. It would be nice if quasar will support webpack 5. The implementation is quite simple. The json file has to be imported as default & the version has to be accessed directly.
The text was updated successfully, but these errors were encountered: