Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deno 2.0 Release Plan #12110

Closed
17 tasks
kitsonk opened this issue Sep 17, 2021 · 10 comments
Closed
17 tasks

Deno 2.0 Release Plan #12110

kitsonk opened this issue Sep 17, 2021 · 10 comments
Milestone

Comments

@kitsonk
Copy link
Contributor

kitsonk commented Sep 17, 2021

Schedule

  • No deadline yet planned.

Scope

Note, at this stage it is still subject to change as items get better refined. This is a working list.

@kitsonk kitsonk pinned this issue Sep 17, 2021
@kitsonk kitsonk added this to the 2.0.0 milestone Sep 17, 2021
@nayeemrmn
Copy link
Collaborator

Has #10628 been considered?

@kitsonk
Copy link
Contributor Author

kitsonk commented Sep 17, 2021

@nayeemrmn yes, including just eliminating the subcommand entirely, in the discussions there was no clear path forward, nor did we evaluate it as having a significant upside in terms of usability, so we just put it aside.

@bartlomieju bartlomieju mentioned this issue Sep 17, 2021
23 tasks
@wojpawlik

This comment has been minimized.

@phil294

This comment has been minimized.

@vwkd

This comment has been minimized.

@kitsonk
Copy link
Contributor Author

kitsonk commented Sep 25, 2021

Folks, this is not the place to discuss Deno release strategy. Please use the discussion topics if you wish to that. This issue is for tracking a planned release. I have marked comments off topic because of this.

@ry
Copy link
Member

ry commented Oct 5, 2021

We've decided to postpone the 2.0 deadline because there are some critical bits we want to figure out still which have uncertain timelines:

  • Should CLI have addEventListener("fetch", _) support out-of-the-box so it can interoperate with Cloudflare Worker and Deno Deploy scripts?
  • Node compatibility (--compat)
  • How does backwards compatibility and effort towards a Deno configuration file interact? Does a default --location interact well with a package.json project directory structure?

I'm going to unpin this issue but leave it open. We do have breaking changes we want to make and will address them - but not yet in November.

@ry ry unpinned this issue Oct 5, 2021
@amithm7
Copy link

amithm7 commented Oct 18, 2021

@ry

Should CLI have addEventListener("fetch", _) support out-of-the-box so it can interoperate with Cloudflare Worker and Deno Deploy scripts?

  • I see that deployctl was archived. So, is the FetchEvent support coming?

@lucacasonato 's archiving comment:

You can now run your Deploy scripts with deno run: deno.com/deploy/docs/running-scripts-locally

@vwkd
Copy link
Contributor

vwkd commented Nov 10, 2021

  • Should CLI have addEventListener("fetch", _) support out-of-the-box so it can interoperate with Cloudflare Worker and Deno Deploy scripts?

@ry I opened denoland/deploy_feedback#107 arguing why designing for compatibility with another service is not a good idea. Irrespective of the why, Cloudflare is transitioning away from the service worker syntax addEventListener("fetch", _) anyways to a default class export with a fetch method 1. Adding this now is just hurting yourself.

Footnotes

  1. export default { async fetch(request, env) { … } } in a .mjs file. Source: https://developers.cloudflare.com/workers/learning/using-durable-objects#instantiating-and-communicating-with-a-durable-object

@bartlomieju
Copy link
Member

Deno 2.0 was postponed indefinitely. I'm going to close this issue to avoid confusion about expected feature set and dates. We will open a new issue when the plan clarifies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants