feat: add Quasar Framework

[yusufkandemir]

Hi, Quasar core team member here 👋

Quasar Framework uses Vite in two different Quasar flavors:

• Quasar CLI with Vite
• Vite plugin for Quasar

Quasar CLI with Vite uses the Vite plugin for Quasar under the hood, so covering the Vite plugin should be a good start. We have quasarframework/quasar#15755 which adds the testing setup, package scripts, etc. that will be run by the Ecosystem CI. We probably do not need to make further changes here if we add tests for Quasar CLI with Vite later, modifying the dedicated package scripts should be enough.

Please let me know if there is anything else we should do, thanks 🙂

Creating it as a draft since the upstream PR is not merged yet, but I wanted to get this out as soon as possible to gather feedback.

A note: pnpm run test quasar --release 4.3.3 works successfully, but pnpm run test quasar fails with the following error:

/Users/yusuf/dev/github/yusufkandemir/vite-ecosystem-ci/workspace/quasar/quasar $> git clean -fdxq
/Users/yusuf/dev/github/yusufkandemir/vite-ecosystem-ci/workspace/quasar/quasar $> yarn install
yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning " > @vitejs/plugin-vue@4.2.1" has unmet peer dependency "vue@^3.2.25".
warning " > @vitejs/plugin-legacy@4.0.2" has unmet peer dependency "terser@^5.4.0".
warning " > @quasar/vite-plugin@1.3.1" has unmet peer dependency "quasar@^2.8.0".
warning " > @quasar/vite-plugin@1.3.1" has unmet peer dependency "vue@^3.0.0".
error An unexpected error occurred: "ENOENT: no such file or directory, stat '/Users/yusuf/dev/github/yusufkandemir/vite-ecosystem-ci/workspace/quasar/quasar/node_modules/vite/node_modules/rollup'".
info If you think this is a bug, please open a bug report with the information provided in "/Users/yusuf/dev/github/yusufkandemir/vite-ecosystem-ci/workspace/quasar/quasar/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
file:///Users/yusuf/dev/github/yusufkandemir/vite-ecosystem-ci/node_modules/.pnpm/execa@7.1.1/node_modules/execa/lib/error.js:59
                error = new Error(message);
                        ^

Error: Command failed with exit code 1: yarn install
warning " > @vitejs/plugin-vue@4.2.1" has unmet peer dependency "vue@^3.2.25".
warning " > @vitejs/plugin-legacy@4.0.2" has unmet peer dependency "terser@^5.4.0".
warning " > @quasar/vite-plugin@1.3.1" has unmet peer dependency "quasar@^2.8.0".
warning " > @quasar/vite-plugin@1.3.1" has unmet peer dependency "vue@^3.0.0".
error An unexpected error occurred: "ENOENT: no such file or directory, stat '/Users/yusuf/dev/github/yusufkandemir/vite-ecosystem-ci/workspace/quasar/quasar/node_modules/vite/node_modules/rollup'".

Tested with Node v18.16.0, Yarn v1.22.19, MacOS Ventura 13.3.1

repo: 'yusufkandemir/quasar',
branch: 'vite-plugin-add-tests',

[dominikg]

please add quasar here: https://github.com/vitejs/vite-ecosystem-ci/pull/208/files#diff-d1bccb5fe17cfd0b67ff454c8a1f2a6d972168a8095f77d93ba0f2cb5adaf7e0R123

[yusufkandemir]

@dominikg done 👍

[patak-dev]

Nice! Looks good to me. Please keep an eye on the #ecosystem-ci channel in Vite Land. We can start tagging you there if there is a red in Quasar before a release.

Just curious, why the build step is different when testing in vite-ecosystem-ci and in the vue-ecosystem-ci here? https://github.com/quasarframework/quasar/blob/933a997b63d148987a61788cd4aa8c25f0eb41f2/package.json#L12

[yusufkandemir]

@patak-dev

I think I'd need the roles for the mentions. So, here is my Discord handle: AzzimothTR#4420

For vite-ecosystem-ci, we specifically test the Vite plugin for the "framework" parts, such as component auto-loading, SCSS variable injection, etc. For vue-ecosystem-ci, we focus on the Vue UI library part. So, the idea is to build/test only the related parts, to consume less CI resources, and to not get sources of error mixed.

But, thanks for being curious about this because I noticed that the test script doesn't work anymore. yarn workspaces automatically link everything locally unlike pnpm which does that only when using the workspace: protocol AFAIK. At the time I created this script our workspace setup didn't have the UI package involved. So, now we need to build all the packages for both ecosystem CIs in order for them to work. I've fixed the build scripts on our end, thanks again.

[dominikg]

i'm not exactly sure what is going on here but the yarn v1 workspace stuff seems to prevent the generated resolutions in workspace/quasar/quasar/package.json from working.

I can't be of much help here as i am not familiar with yarn v1 and won't start learning about it now. Please update the branch to latest main too (when i cloned it i got an outdated version with pnpm@7) This might be because you initially forked it before we updated it.

[yusufkandemir]

@dominikg, it respects the resolutions and symlinks the nested modules. But, it probably gets confused due to the pnpm node_modules structure in the resolved module, creating faulty symlinks. This is an example symlink Yarn created: node_modules/vite/node_modules/esbuild -> ../../.pnpm/esbuild@0.17.5/node_modules/esbuild (relative to workspace/quasar/quasar, resolves to non-existent path: workspace/.pnpm/...)

When I removed node_modules in workspace/vite/packages/vite and used yarn to install dependencies, then re-trigger the install process in workspace/quasar/quasar, it worked fine. It required two minimal changes in the Vite codebase to keep Yarn happy:

• Adding "version": "0.0.0" to packages/vite/src/types/package.json
• Adding "version": "0.0.0" to packages/vite/types/package.json

[dominikg]

This has not been an issue in any of the other tests in vite-ecoystem-ci and i'm not sure if i understand you correctly but you can't be suggesting to switch vite to yarn to solve this.

fyi @sapphi-red ^ the package.json in vite/types had been added by you.

[sapphi-red]

I think it's fine with adding version field to those files.

But I'm curious about the reason of using yarn v1. Yarn v1 is already frozen and by using nodeLinker: 'node-modules' yarn v3 will work like v1 (i.e. without pnp).
https://yarnpkg.com/getting-started/migration#step-by-step

[yusufkandemir]

@dominikg I am not suggesting Vite switch to Yarn, I shared my findings hoping they would help. Even if the version field is added, the ecosystem-ci script would need to use Yarn for Vite when cloning, installing, building, etc.

@sapphi-red because it works. We plan to migrate to pnpm and use workspaces for the whole repo. But, we are in the middle of significant changes such as migrating our code to ESM and supporting it in userland as well. For the same reason, we don't want to switch to Yarn v3 now, we'll move away from it anyway. I have just given Yarn v3 a try and it didn't work out of the box, some packages didn't resolve correctly, and the migration would take extra effort, which is not worth it at the moment.

If we don't have an easy solution to address the problem, I suggest running Quasar tests only with stable releases if possible, until we figure out a solution or migrate to pnpm.

[dominikg]

Even if the version field is added, the ecosystem-ci script would need to use Yarn for Vite when cloning, installing, building, etc.

This is not going to happen. vite repo uses pnpm and that's what we have to use for installation.

Curious how this works for you in vue-ecosystem-ci but not in vite?

[patak-dev]

That's a good question. @sodatea do you know why Vue using pnpm wasn't an issue in vue-ecosystem-ci for Quasar? Linking the PR for reference vuejs/ecosystem-ci#7

[sodatea]

Because the vue ecosystem-ci uses a local registry, so the vue package there is not linked, but actually downloaded from the registry.
This setup makes local debugging a bit more difficult but avoids many edge cases.

[patak-dev]

I wonder if it makes sense for ecosystem-ci to use the local registry as an opt-in only for some projects. As a flag passed to the test, localRegistry: true. Then we only pay for a degraded local experience on these projects.

[yusufkandemir]

We have migrated from Yarn to pnpm: quasarframework/quasar#16990
pnpm run test quasar works fine now, so I think the PR is finally ready to merge.

[patak-dev]

Great news @yusufkandemir! Let's merge this one and tried it out 👍🏼