-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
tracking: Deno 2 subcommand, flag and symbol removals #22079
Comments
There's a proposal to deprecate |
Should we track |
Remind me, which ones? |
Luca proposed to "deprecate |
How about actually turning them off when the DENO_FUTURE env is enabled? #22318 |
Yes, that is the current plan 🙂 |
Update: the following APIs will no longer be completely removed in Deno v2, and I've updated the list accordingly:
|
According to Deno Deploy's API reference, none of these APIs exist on Deno Deploy. I suggest we proceed with these removals, starting with being included in Deno 2 RC. |
Towards #22079 --------- Signed-off-by: Asher Gomez <[email protected]>
Towards #22079 --------- Co-authored-by: Bartek Iwańczuk <[email protected]>
Towards #22079 --------- Signed-off-by: Asher Gomez <[email protected]>
….rid` (#25446) Towards #22079 --------- Signed-off-by: Asher Gomez <[email protected]>
Towards #22079 --------- Signed-off-by: Asher Gomez <[email protected]>
Towards #22079 --------- Signed-off-by: Asher Gomez <[email protected]>
Towards #22079 --------- Signed-off-by: Asher Gomez <[email protected]>
Towards #22079 Signed-off-by: Asher Gomez <[email protected]>
All done now 🙂 |
The following table contains all of the subcommands, flags and symbols to be removed in Deno 2.0.0. Some symbols will be soft removed, meaning that their types will be removed, but their functionality will live on, as to not break too much code. Maintainers, please update as needed.
Migration documentation can be found here: https://docs.deno.com/runtime/manual/advanced/migrate_deprecations/
deno bundle
deno vendor
--allow-none
--jobs
--ts
--trace-ops
--unstable
Deno.Buffer
Deno.close()
Deno.Closer
Deno.Conn.prototype.rid
Deno.ConnectTlsOptions.certChain
Deno.ConnectTlsOptions.certFile
Deno.ConnectTlsOptions.privateKey
Deno.copy()
Deno.customInspect
Deno.fdatasync[Sync]()
Deno.File
Deno.flock[Sync]()
Deno.FsFile.prototype.rid
Deno.fstat[Sync]()
Deno.FsWatcher.prototype.rid
Deno.fsync[Sync]()
Deno.ftruncate[Sync]()
Deno.funlock[Sync]()
Deno.futime[Sync]()
Deno.isatty()
(soft)Deno.iter[Sync]()
Deno.Listener.prototype.rid
Deno.ListenTlsOptions.certChain
Deno.ListenTlsOptions.certFile
Deno.ListenTlsOptions.keyFile
Deno.metrics()
Deno.read[Sync]()
Deno.readAll[Sync]()
Deno.Reader[Sync]()
Deno.resources()
Deno.run()
(soft)Deno.Seeker[Sync]
Deno.seek[Sync]()
Deno.serveHttp()
(soft)Deno.Server
Deno.shutdown()
Deno.stderr.prototype.rid
(soft)Deno.stdin.prototype.rid
(soft)Deno.stdout.prototype.rid
(soft)Deno.TcpConn.prototype.rid
Deno.TlsConn.prototype.rid
Deno.TlsListener.prototype.rid
Deno.UnixConn.prototype.rid
Deno.write[Sync]()
Deno.writeAll[Sync]()
Deno.Writer[Sync]
new Deno.FsFile()
window
The text was updated successfully, but these errors were encountered: