`.postcssrc.js` requires `autoprefixer` but it isn't listed as a dependency. about quasar-starter-kit

[rstoenescu]

Hi,

"autoprefixer" is supplied by "@quasar/app". Highly recommending (as in the docs) to use a better package manager: yarn, for a headache-free experience.

[RaviH]

@rstoenescu quasar is amazing. Period. pnpm support, while not important, would be nice to have.

I get:

~/todo-app/.quasar/client-entry.js in multi ./node_modules/.pnpm/[email protected][email protected]/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 (webpack)/hot/dev-server.js ./.quasar/client-entry.js

[pinghe]

quasarframework/quasar#7581

We have plans to create a CLI based on Vite instead of Webpack and that will allow us to officially support Yarn 2

[zkochan]

I am not sure what a "better package manager" means. If this issue is because a non-declared dependency is used, then this will also fail with Yarn v2.

[rstoenescu]

Maybe my wording was "off". So here's another try.

You can also install the same "autoprefixer" version in your project folder and still use pnpm. But if you install packages supplied by quasar/app yourself, you are essentially throwing away all the stability that q/app offers out of the box. We thoroughly test packages and pin them to "safe" versions (and also upgrade them really fast) so that the developers can focus on their work rather than the tooling. We've had so many incidents where certain versions of some packages broke stuff. Our philosophy is to make everything easier for you, not harder.

So aside from the possibility to make pnpm play nicely with Quasar projects (available today), my personal opinion, and everyone can feel free to disagree with me, is that a package manager should not matter so much when compared to the quality of the UI that you can make with a framework (including exceptional out of the box support for all platforms, be them desktop, mobile or hybrid) and the overall experience that you get from it -- the ability to focus on your end-result which is the only thing that your customers will care about.

Bottom line, let's make great apps and not build walls against each other.