Retake @nx/deno plugin

[guillempuche]

Do you have plans to update the plugin?

https://www.npmjs.com/package/@nx/deno

[andrewoffenden]

This is unfortunate. Any updates on why?

[thenglong]

Deno 2 is out and it's very compatible with node. Is there a plan to re-add Deno as the default support?

[exsesx]

I'd love to see Deno support as well, mainly in terms of multiple TypeScript projects and how Deno handles them. Right now, managing TSC with all config files can become complicated really quickly without proper referencing, etc.

[hemedani]

Deno v2 initially support workspace and monorepo, do not need for something like nx anymore, it's work perfectly for me.

[guillempuche]

@hemedani, Nx strength is in testing & building dozens of packages. It caches the untouched code.

As you said, Deno, also Yarn, pnpm... perfectly work well with monorepos/workspaces. Another thing is to work well at scale.

[hemedani]

@guillempuche
Yah, Nx is very good at testing & building and CI/CD process, but Deno natively add lots of thing like:

• deno fmt can now format HTML, CSS, and YAML
• deno lint now has Node specific rules and quick fixes
• deno test now supports running tests written using node:test
• deno task can now run package.json scripts
• deno doc’s HTML output has improved design and better search
• deno compile now supports code signing and icons on Windows
• deno serve can run HTTP servers across multiple cores, in parallel
• deno init can scaffold now scaffold libraries or servers
• deno jupyter now supports outputting images, graphs, and HTML
• deno bench supports critical sections for more precise measurements
• deno coverage can now output reports in HTML

Also, it's add standard library for many things like:

@std/testing ==> jest
@std/expect ==> chai
@std/cli ==> minimist
@std/collections ==> lodash
@std/fmt ==> chalk
@std/net ==> get-port
@std/encoding ==> rfc4648

I think we can do everything nx do with native deno features, especially at scale, because deno is very performant and stable in V2