8000 Tags · Rachelmorrell/ember-cli · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Tags: Rachelmorrell/ember-cli

Tags

v3.4.0-beta-fixed-package-info-cache

Toggle v3.4.0-beta-fixed-package-info-cache's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request ember-cli#7983 from ember-cli/beta-remove-logging

Remove unneeded logging.

v3.4.0-beta.3

Toggle v3.4.0-beta.3's commit message
Release v3.4.0-beta.3

v3.4.0-beta.2-beta3

Toggle v3.4.0-beta.2-beta3's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request ember-cli#7983 from ember-cli/beta-remove-logging

Remove unneeded logging.

v3.4.0-beta.soon-3

Toggle v3.4.0-beta.soon-3's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request ember-cli#7983 from ember-cli/beta-remove-logging

Remove unneeded logging.

OMG

Toggle OMG's commit message
Stabilize + Lock-down add-on discovery order.

The recent PackageInfoCache work accidentally re-ordered dependencies, applying devDependencies after dependencies rather then before. This resulted hard to diagnose but breaking behavior.

An interim solution, sorted dependencies wholesale lexicographically but this resulted in other breakage.

To address all this, this PR:

* restores the original precedence (devDependencies < dependencies)
* ensures ordering within devDependencies or dependencies is always lexicographical (regardless of the order within package.json)
* if duplicates exist between devDependencies and dependencies, we take a “element of least surprise approach” they are de-duped, and the “last occurrence” encountered solidifies the ordering.  order([a,b,c,a]) => [b,c,a]
* thorough testing to lock down the ordering, ensuring future work

This aims to remove preventable ambiguity. For those requiring explicit ordering beyond what we support out of the, they are encourage to use the before/after API. This will create an explicit edge, forcing order…

This PR was tested against a very large real world application. This application has 40+ engines, and a huge number of add-ons. This application was also the one which detected the above issues. After this PR everything works!

v3.4.0-beta.2

Toggle v3.4.0-beta.2's commit message

Verified

This commit was signed with the committer’s verified signature.
Release v3.4.0-beta.2.

v3.4.0-beta.1

Toggle v3.4.0-beta.1's commit message
Release v3.4.0-beta.1

v3.3.0

Toggle v3.3.0's commit message
Release v3.3.0

v3.2.0

Toggle v3.2.0's commit message
Release v3.2.0

v3.1.4

Toggle v3.1.4's commit message

Verified

This commit was signed with the committer’s verified signature.
Release v3.1.4.

0