Bump js from 0.6.7 to 0.7.0 in /pkgs/test

[dependabot]

Bumps js from 0.6.7 to 0.7.0.

Commits

• dfff771 Version 0.7.0.0
• df6ae38 Version 0.6.21.3
• ce57b84 Version 0.6.21.0
• c2e4ca3 svn merge -r 26292:26492 https://dart.googlecode.com/svn/branches/bleeding_ed...
• 0b2b0fe Version 0.6.19.0 .
• 2c5963a Version 0.6.18.0 .
• 61f7d41 Version 0.6.17.0 .
• e97cdf2 Version 0.6.16.0 .
• c3a1e1a Version 0.6.15.2 .
• 8e602bd Version 0.6.15.0 .
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[natebosch]

@srujzs - Do you know if it should be safe to expand the constraint and allow >=0.6.0 <0.8.0?

[jakemac53]

I am curious what the actual breaking changes are here? The changelog doesn't list anything obviously breaking https://pub.dev/packages/js/changelog#070?

[srujzs]

I am curious what the actual breaking changes are here? The changelog doesn't list anything obviously breaking https://pub.dev/packages/js/changelog#070?

It's a bit subtle (I'll amend the changelog to be more specific), but this is the relevant comment:

Moved annotations to single location in dart:_js_annotations. This makes it easier to avoid collisions with dart:js_interop's @JS.

We have two @JS annotations - one that is visible through package:web and the other through dart:js_interop. We did this to avoid a breaking change in the meaning of the annotation (particularly around soundness of return types). Due to the way Dart resolves definitions, the package definition is always preferred over an SDK definition. This is bad, because users who import both interop libraries and use @JS will silently use the package:js definition. To avoid this, we added a change to move the annotation from package:js to a Dart library (dart:_js_annotations) and export it so that a collision actually occurs. However, any code that was importing both libraries and using @JS will now break if they had a js: ^0.6.0 constraint. So, I opted to make this a breaking change.

Do you know if it should be safe to expand the constraint and allow >=0.6.0 <0.8.0?

It should likely be >=0.6.4 <0.8.0 since the previous 0.6.X versions don't include stuff that this package uses like @staticInterop. That modified constraint should be okay I believe since package:test itself doesn't have any collisions of @JS. Packages that depend on package:test can use any package versions between that version range.

[kevmoo]

PTAL