Spike nx for monorepo managment
#2776
Labels
🕵️ investigate
Needs investigation
⚙️ technical
Technical improvements, maintenance or other issues that are not directly linked to a feature
Milestone
Comments
mimarz
added
⚙️ technical
mimarz
changed the title
nx for monorepo managment
mimarz
added a commit
that referenced
this issue
Dec 12, 2024
A simple way to type checking all our projects now without relying on third party for now., until we have a look at #2776 - run `yarn types` to run this check locally - Checks gh action is noticeably slower now with runtime going for 50s to 1min 20s. I think we are ok with this for now since we have other stuff running longer on PRs. - Using [yarn workspaces foreach](https://yarnpkg.com/cli/workspaces/foreach) we run `types` script on all our packages that have it defined. - Fixed a couple of linting errors and mistakes deleting stuff that was used - Added `types` script on relevant projects Current type checked projects ``` [@digdir/designsystemet] [@digdir/designsystemet-react] [@designsystemet/storybook] [@repo/components] [figma-plugin] [storefront] [theme] ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Spike on using nx for managing our monorepo.
We have more and more apps & libraries that are depandant on eachother that needs to be rebuilt or typecheck when changes are made. Having some parts cached might also help for CI runs on PRs.
In the future we might want to also have some test apps for generic vite/nextjs/webpack project.
This will add more complexity and dependencies to our project but the benefit of catching errors might out weigh this if its easy and fast to setup and use.
The text was updated successfully, but these errors were encountered: