Repository navigation
chore: release - #253
Merged
Merged
chore: release#253
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
onsystem@0.10.3
Patch Changes
#250
5466dee- A design-system package whose tokens are a Tailwind v4 theme partial (@theme, with no@import "tailwindcss", since the app imports Tailwind) no longer turns offno-hardcoded-spacingin the apps that read its config. In a project on Tailwind v4 (@tailwindcss/postcss,@tailwindcss/viteor@tailwindcss/cliin itspackage.json, ortailwindcssin a range other than v3's, such as^4), such a theme gets Tailwind's default spacing unit and radius scale, as a stylesheet that imports Tailwind does, unless it clears them (--spacing-*: initial).p-[13px]is reported again, withp-3as the nearest step.A component imported through a subpath export that leads to a source file that does not exist, such as
<Tooltip>from@acme/ui/components/tooltipwhere"./components/*": "./src/components/*.tsx"has nosrc/components/tooltip.tsx, is reported byno-unknown-componentin workspace apps that read the package's config, as it already was in apps that install the package. It was said not to have been checked, with advice to add the missing files to "components". An import whose export leads to a build folder (dist/) with no file there, as before the package is built, is still said not to have been checked, whatever its sources are named.In an app whose design-system package publishes neither its component sources nor their type declarations,
list_components,get_componentandinspect --explainnow say so, and what its team can do, instead of telling you to check the "components" globs in the config, which would not help.initin a design-system package addsONSYSTEM.mdtofilesin itspackage.json, next to the config, so the teams of apps that install the package get the guide innode_modules, unlessfilesleaves it out ("!ONSYSTEM.md").