refactor: remove relative onyx imports from docs #2096
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We were currently using direct/relative imports for onyx components used in our VitePress docs. This required custom Vite/tsconfig options and might not be intuitive for new/External contributors taking a look at our codebase.
With our turbo repo setup, we can easily import directly from
sit-onyx
and turbo repo will make sure to build the components first. Like this our docs is just a regular consumer of thesit-onyx
package, just like our playground and demo app.