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

Upcoming deprecation of legacy HTML and JavaScript libraries #6278

Open
MaryaBelanger opened this issue Dec 13, 2024 · 0 comments
Open

Upcoming deprecation of legacy HTML and JavaScript libraries #6278

MaryaBelanger opened this issue Dec 13, 2024 · 0 comments
Labels
a.libraries Relating to the Dart standard libraries. dev.interop Relates to use of native code as part of your Dart app e2-days Can complete in < 5 days of normal, not dedicated, work p2-medium Necessary but not urgent concern. Resolve when possible. target.web Target apps on the web platform

Comments

@MaryaBelanger
Copy link
Contributor

From Dart Announcements:

Earlier this year, we launched a new set of Dart libraries for JavaScript interop and package:web to access browser features. These APIs are designed to maximize performance, minimize compiled code size, and enable compatibility when your Dart and Flutter applications target JavaScript, WebAssembly, or both.

Now that these new APIs have been out for a year, it's time to sunset the legacy APIs that have been replaced. Starting with the first stable release of Dart and Flutter in 2025, the following dart: libraries will be deprecated:

  • dart:html
  • dart:indexed_db
  • dart:js
  • dart:js_util
  • dart:svg
  • dart:web_audio
  • dart:web_gl

We will also deprecate package:js.

While these APIs will still be available, developers will start seeing warnings about their use. Packages that depend on them will also see their score on pub.dev drop. Final removal of the legacy Dart SDK libraries is being discussed for the end of 2025.

To learn about alternatives, read the JavaScript interoperability guide. If you have issues, feel free to comment on the tracking issue.


To do: determine whether deprecation notices should be placed around the site, or content should be removed

@parlough parlough added p2-medium Necessary but not urgent concern. Resolve when possible. e2-days Can complete in < 5 days of normal, not dedicated, work target.web Target apps on the web platform dev.interop Relates to use of native code as part of your Dart app a.libraries Relating to the Dart standard libraries. labels Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a.libraries Relating to the Dart standard libraries. dev.interop Relates to use of native code as part of your Dart app e2-days Can complete in < 5 days of normal, not dedicated, work p2-medium Necessary but not urgent concern. Resolve when possible. target.web Target apps on the web platform
Projects
None yet
Development

No branches or pull requests

2 participants