Proposal: Migrate to JSR-oriented codebase about deno_std HOT 5 CLOSED

Steps needed for this migration:

• Run _tools/convert_to_workspace.ts and commit the changes.
• Start using https://github.com/denoland/bump_workspaces for upgrading versions of submodules (This happens independently from CLI release)

from deno_std.

We plan to do this migration right after Deno CLI 1.43 release (which is scheduled on 4/24).

from deno_std.

As you say, the sooner we make this move, the sooner we can stabilise the Standard Library, and that would be great for everyone. I'm very much in favour of this.

To me, workspaces support in both JSR and the Deno runtime are sufficiently established for the change. I haven't had any issues with workspaces functionality so far. I also think stability in the Standard Library is what is desired by users the most.

CC @ry and @rbetts

from deno_std.

The following PRs must be merged right before the JSR cutover:

• #4642
• #4643
• #4644

from deno_std.

We plan to do this migration right after Deno CLI 1.43 release (which is scheduled on 4/24).

JSR cutover didn't happen yet because CLI 1.43 release was postponed to the next week because of performance issue

from deno_std.