Adam Haglund
Adam Haglund
From looking into it more, it seems like using `--mode staging` that [the docs recommend for building "production-like behavior, but with slightly different env variables"](https://vitejs.dev/guide/env-and-mode.html#modes) also changes `import.meta.env.PROD` to be...
Which probably would be why it also seems to cause `plugin-react` to use the development react version
The pnpm support seems to only recognize the top-level dependencies from my testing of running `qnm` in any repo using pnpm
https://github.com/BeeeQueue/qnm-repro If you install using npm it shows 700~ deps, and if you remove `node_modules` and install using pnpm it shows 8
With this libraries that need tree-shaking would be able to use esbuild directly, right now you have to run it through either rollup or webpack to not have one big...
Can confirm this bug, had to downgrade to `3.5.0` to be able to use the package
I've run into the same problem. This happens due to the behavior of setting `` tags to `scoped`. This gives all elements in the component a unique `data-v-[hash]` property, which...
Currently this service is just a REST API for getting data from [`anime-offline-database`](https://github.com/manami-project/anime-offline-database/). This feature would increase the scope to an ID mapper as well, which I've been thinking about...
It's still more cumbersome than just basing it on an already existing env variable and/or a boolean passed into the constructor.
Also getting this transferring from Windows 11 to a Linux machine (Steam Deck) on LAN. It worked before I upgraded (on W10).