You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously @EisenbergEffect released new parser in aurelia-binding v2 to make it a safe opt-in. But since then, aurelia core libs have been updated to depend on v2.
But if you have some 3rd party plugin (very likely) still asks aurelia-binding^1.x.x in the package.json, you end up with 2 versions of binding in your node_modules (one direct, another one under the plugin folder).
webpack tries to respect the plugin's dependency, hence bundled 2 versions of aurelia-binding.
The end result is all sorts of weird bugs. The first thing you can notice is the repeat.for creates extra entry on array push. Due to Array.prototype.push has been patched twice.
To solve the problem, based on the audit result of all packages depend on aurelia-binding
1. release aurelia-binding v1.8.0, make sure it's tagged as latest on npmjs registry. 2. update all core packages (7) back to "aurelia-binding": "^1.0.0". 3. reach out to all non-core (7) but on ^2.0.0, to update them back to "aurelia-binding": "^1.0.0".
Note: updating core packages back to "^1.0.0 | ^2.0.0" doesn't solve everything, as you need to ask the same for non-core (7) but on ^2.0.0. So why not just upgrade all of them back to ^1.0.0 to simplify dependency.
Update: decision was made to keep v2.
The text was updated successfully, but these errors were encountered:
Originated from aurelia/templating#575 (comment)
Previously @EisenbergEffect released new parser in
aurelia-binding
v2 to make it a safe opt-in. But since then, aurelia core libs have been updated to depend on v2.But if you have some 3rd party plugin (very likely) still asks
aurelia-binding
^1.x.x
in thepackage.json
, you end up with 2 versions of binding in your node_modules (one direct, another one under the plugin folder).webpack tries to respect the plugin's dependency, hence bundled 2 versions of aurelia-binding.
The end result is all sorts of weird bugs. The first thing you can notice is the repeat.for creates extra entry on array push. Due to
Array.prototype.push
has been patched twice.To solve the problem, based on the audit result of all packages depend on
aurelia-binding
Core packages (7) all on
^2.0.0
Non-core (7) but on ^2.x.x
Non-core (45) on ^1.x.x
1. releaseaurelia-binding v1.8.0
, make sure it's tagged as latest on npmjs registry.2. update all core packages (7) back to"aurelia-binding": "^1.0.0"
.3. reach out to all non-core (7) but on^2.0.0
, to update them back to"aurelia-binding": "^1.0.0"
.note most of them are controlled by core team member.4. update cli to use https://github.com/darrenscerri/duplicate-package-checker-webpack-pluginthis warns user about duplicated packages.Update: decision was made to keep v2.
The text was updated successfully, but these errors were encountered: