Is support for Deno and JSR in this project's roadmap?

[nberlette]

Howdy! I discovered @manypkg/get-packages while browsing the changesets source code and was disappointed to find it currently doesn’t support Deno.

I’m opening this issue to discuss whether the maintainers would consider adding support for Deno and JSR in a future release. With the Deno CLI now in the 2.2 cycle, it’s evolved significantly—now capable of managing monorepo workspaces, among other things.

Deno implements nearly every builtin node:* module, and NPM packages are directly accessible via the npm: specifier prefix. It also supports using package.json files interchangeably with deno.json files to define package configurations.

That said, many JSR package authors (myself included) opt for deno.json for various reasons. As a result, myself and others are currently unable to take full advantage of this tooling or other ecosystem tools that depend on it (for example, changesets). However, even if I switched all my packages to use package.json, I’m not sure the tool would work well with Deno as it stands—since it essentially assumes it’s operating in a Node environment.

I’m eager to hear your thoughts and discuss potential solutions.

Thank you for your time and consideration!

[Andarist]

@nberlette we could consider supporting Deno and JSR but, at the very least, some plan for that would have to be laid out by somebody who is familiar with that ecosystem. I don't know what would exactly be required to make it work, what are the conventions used by this ecosystem etc.

[fry69]

I gave this a try #262 , the CLI functionality is not yet ready, but if you want you can already have a look and comment.

Update: This seems not the way, I will look for another approach for my specific goal to get some kind of changesets support working for Deno.