-
Yusuf Kandemir authored
* chore: migrate to pnpm * feat(app-vite&app-webpack): improve package manager references in banners * chore: remove npm reference in dev app uploader page * docs: upgrade contribution guide * chore: correctly include extras in workspaces * chore: include create-quasar in workspaces * chore: centralize .editorconfig * chore: remove yarn.lock * chore: only allow pnpm * chore: centralize linting packages and config * chore: create shared eslint config package * chore: remove redundant pnpm.peerDependencyRules.ignoreMissing it needs to be specified in the root since we are using pnpm workspaces but, it doesn't seem to be changing any behavior, so it's redundant * chore: include cli in workspaces * ci: ensure pnpm is installed and cache is set correctly * chore: generate pnpm lock file after rebase * chore: tidy up eslintignore * chore: setup root lint script * chore: include app-webpack in workspaces * chore: update vscode config * chore: update .github/CONTRIBUTING.md * chore: regenerate lock file * ci: fix create test project script after migrating to pnpm workspaces, some behavior got changed 1. prompts package named imports are not working. This is probably due to switching to a different version during migration, rather than a pnpm specific issue. 2. When using pnpm to create the test project, it becomes part of the monorepo, which makes it fail to install properly. * ci: fix weird test creation test issue with yarn * Revert "ci: fix weird test creation test issue with yarn" This reverts commit 5fcaa12ae1caf22ee7906048dc3ee9755dda1b4a. * ci: fix weird test creation test issue with yarn https://github.com/yarnpkg/yarn/issues/9015 * ci: apply skip yarn corepack check to other scripts as well but still keep it in create-test-project script to avoid the problem when executing the script in different environments * ci: cache Cypress binary to fix tests on pr workflow * ci: install Cypress binary when cache does not exit and correctly cache it * chore(ui): fix tests not being able to run
After you've reviewed these contribution guidelines, you'll be all set to
contribute to this project.