-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat/turborepo #14
Feat/turborepo #14
Conversation
This change makes sure that the features cover 95% of all browsers.
This change configurates next.js to run with turborepo. Second, it configures eslint to work with jest and storybook, as well as adding good rules to keep code consistent across the repository. It also adds some stylelint and postcss configuration. BREAKING CHANGE: CI scripts will not work. CI and Vercel need to be configured to run with the new code.
This change adds a lighthouse.yml file which checks lighthouse statistics of the vercel preview URL to give useful stats on PRs.
This change adds issue templates for bug reports and feature requests.
This change adds groups for storybook and testing dependencies.
Analyzes security health of the repository and helps with security best practices.
Pre-commit is a framework for managing and maintaining multi-language pre-commit hooks.
I don't know if there is a way to run many tests asynchronously before finally running the release action - but for now I will just have it be manual. I also just don't want to release a millino versions (hyperbolic) for small changes.
CodeQL is a tool for open source projects, or private ones witha license, to analyze code for vulnerabilities based on their own engine.
Going off of the repository on nodejs.org, I decided that their setup would probably be best given that I'm using a similar (but not exactly the same) configuration.
Checks that dependencies are scanned for known vulnerable versions of packages.
This change takes full advantage of turborepo caches to perform faster linting and testing.
Nodejs.org has a really good workflow where they run CI tasks on PRs only when a label is applied. This is really useful when you have WIP PRs that aren't quite done yet, or when you need to correct changes.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
🎉 This PR is included in version 2.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
This change does the following:
1. Configures next.js to run with turborepo
2. Moves dependencies around from devDeps to dependencies
in order to optimize build times through
pnpm i -P
.3. Adds more github actions and reconfigures previous ones so
that they work with turborepo
4. Adds Storybook and Jest for testing
5. Reconfiguring package.json scripts to work with turborepo
6. Add Issue templates
7. Add Codeowners file
8. Add pre-commit-config
9. Change dependabot to include storybook and Jest groups
Validation
I ran the scripts in the checklist and it worked as it should locally.
Related Issues
Check List
npx turbo format
to ensure the code follows the style guide.npx turbo test
to check if all tests are passing.npx turbo build
to check if the website builds without errors.