[dgesteves-release]

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.2

Patch Changes

• #242 bfea680 - The MCP server no longer keeps a load that failed. A config that was invalid when the server started (a typo in rules, a bad glob) is read again on the next request, so fixing it is enough, without restarting the server. Before, every request returned the first error until the client restarted the server, even with --watch. In a project found from the path a tool call names, a project whose config fails no longer counts as a project found, and switching from onsystem.config.mjs to onsystem.config.json, as the error says, now takes effect. Two paths to the same project, through a link or in another letter case on macOS or Windows, load it once instead of counting as two projects. A design system whose first build fails is built again by the next request.

  An edited onsystem.config.mjs, .js or .ts is read again: the server logged "reloaded" but kept the rules it loaded first, because Node.js returns a module it has already imported. A JSON config was not affected. A module that the config imports is not read again: restart the server after editing one.

  A --root that is no project but holds projects in its folders, such as a folder of repositories that --root ${workspaceFolder} names when the editor has their parent open, is no longer served as one project that mixed their tokens and suggested fixes with another repository's tokens. The server answers each request from the project of the absolute path it names, as it does when started outside any project, and asks for a path until one is named. Only a path inside that folder is answered, from the project in it that holds the file, never from a monorepo root above the folder. Paths are compared with links resolved: a path outside the folder, one that leads outside it through a link, or a relative one gets an error that asks for the absolute path of a file in it, and a workspace in the folder serves only its packages that are in it, naming the others in the server's log. A project or workspace package in the folder that is replaced by a link while the server watches it is not read from where the link leads: the server keeps the design system it had read from the folder. The same holds for a client's root. For zero config in such a folder, **/*.tokens.json no longer reads the token files of the projects in it, so check run there gives no fix from another project either.