-
Notifications
You must be signed in to change notification settings - Fork 211
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
Fix dependency on discontinued js package #3861
Comments
This should have been completed in #3793 |
@jakemac53, that removed actual usage of js, but it's still listed as a dependency: build/build_runner/pubspec.yaml Line 34 in 7dbcd85
And it looks like build_web_compilers still depends on it as well. |
Weird, I didn't see any more diagnostics, but yeah any remaining usage should be removed |
Oh you are saying it's an unused dependency that just didn't get cleaned up |
In build_runner, yes, in build_web_compilers, there's an actual use (but there's an ignore_deprecated_member_use, so that's probably why you didn't see diagnostics) |
Here's build/build_web_compilers/web/stack_trace_mapper.dart Lines 27 to 28 in 7dbcd85
|
ohhh, we just ignored it 🤕 |
Yes, I added the ignore as it broke CI :) I guess it's okay if I get to this in a week or two, nothing's on fire? |
I don't depend on build_web_compilers, but can we at least remove the unused dependency on (It's not breaking me, it's just that it's a tiny, separate patch that I'm sure others will hit pretty soon. Enjoy your weekend!) |
They'll just see a warning, I think? Or is there actual breakage? |
Just a warning, but again, it's a one-line fix and I'm certain some people will read "deprecated" and freak out (see: npm ecosystem). |
I'm in the middle of a huge refactoring, it's not straightforward to do a release right now. Hopefully this week. |
The package js, which build_runner has a dependency on, was marked discontinued with release 0.7.2 on Feb. 12, 2025. The recommendation is to use js_interop instead moving forward per https://pub.dev/packages/js.
The text was updated successfully, but these errors were encountered: