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
I don't know if it's a bug but I tried to upgrade postcss-loader npm package (from v1.3.3 by default in Quasar to latest v2.0.5) but after upgraded, error there is an error "No PostCSS Config found in (...)" when compiling with _quasar dev
The problem is solved when I downgrade postcss-loader to v1
I think postcss-loader configuration have changed a lot from v1 to v2, but maybe if you want to improve this package in Quasar for futures releases.
The text was updated successfully, but these errors were encountered:
v2 (must have been released a few days ago) contains breaking changes (by semver convention), so it can't work by default with current configuration. The default Quasar template is regularly updated to use latest and greatest, so no thing to worry about.
What you can do to speed things up (as I'm overloaded on v0.14 work) is to investigate and apply the changes in a PR pls? Otherwise it will take some time as this is not a "must do" in the Quasar todo queue.
Hi,
I don't know if it's a bug but I tried to upgrade postcss-loader npm package (from v1.3.3 by default in Quasar to latest v2.0.5) but after upgraded, error there is an error "No PostCSS Config found in (...)" when compiling with _quasar dev
The problem is solved when I downgrade postcss-loader to v1
I think postcss-loader configuration have changed a lot from v1 to v2, but maybe if you want to improve this package in Quasar for futures releases.
The text was updated successfully, but these errors were encountered: