bundled dependencies

[calvinmetcalf]

we bundled our less common dependencies with version 2.2.0, but this immediately causes issues, specifically with yarn (yarnpkg/yarn#1774 and the tl;dr is that the issue was installing yarn not using yarn). The issue seemed to be about upgrading and the dependencies changing place. So we may need to come up with a different way to bundle them.

[mcollina]

IMHO we are in an impossible situation. It shouldn't matter about using bundledDependencies or not.

Anyway, we must bump the major if we want to try again, or have our own version of citgm.

[calvinmetcalf]

re citgm it was not fresh installs from what I could tell, just upgrades

On Tue, Nov 15, 2016 at 1:55 AM Matteo Collina [email protected]
wrote:

IMHO we are in an impossible situation. It shouldn't matter about using
bundledDependencies or not.

Anyway, we must bump the major if we want to try again, or have our own
version of citgm.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#247 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABE4n8F70FOjfi164cHTx-nD3c06U1Tiks5q-VdXgaJpZM4KxpbJ
.

[mcollina]

Ahum. Looks like it's an npm bug in computing the tree. Sigh. Whenever we bump the major, it will be a nice change to add.