Created
December 28, 2015 17:13
-
-
Save sgress454/e3d76fe6cd10db5a1d0d to your computer and use it in GitHub Desktop.
Notes on upgrades from v0.11.3 dependencies to now
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Following is the list of top-level non-development dependencies with their versions in v0.11.x and notes detailing the version they are upgraded to in v0.12.x (if any) and why. New dependencies (like `consolidate`) have notes explaining the choice of current version. | |
| ├── anchor@~0.10.5 (ours) | |
| ├── [email protected] -> 0.10.5 (has changelog, lots of bug fixes and good stuff) | |
| ├── captains-log@~0.11.11 (ours) | |
| ├── [email protected] -> 1.1.2 (no changelog, but seems to be just bugfixes and it's only used for logs) | |
| ├── [email protected] -> 2.9.0 (has changelog, bugfixes et al) | |
| ├── [email protected] -> 2.29.1 (required by our express version) | |
| ├── [email protected] (latest) | |
| ├── [email protected] (latest is just react/promises stuff) | |
| ├── [email protected] (upgrade causes angst for connect; only used briefly ) | |
| ├── [email protected] -> 1.0.6 (minor fixes) | |
| ├── [email protected] -> 2.3.4 (we've been using it, guess it works, could use some tests) | |
| ├── [email protected] (latest) | |
| ├── [email protected] -> 3.20.2 (thoroughly tested) | |
| ├── [email protected] (latest) | |
| ├── [email protected] -> 0.18.4 (been using it, only used on tests, further changelog looked meh) | |
| ├── [email protected] -> 5.0.15 (only used in one spot, been using, but v6 has breaking changes) | |
| ├── [email protected] -> 0.4.5 (been using) | |
| ├── [email protected] (latest) | |
| ├── [email protected] -> 0.6.0 (been using, but 0.7.0 is mostly dep changes of ~ to ^, tested w/ rigging) | |
| ├── [email protected] -> 0.13.0 (seems fine) | |
| ├── [email protected] -> 0.5.1 (tested w/ project, changelog looks good) | |
| ├── [email protected] (updating breaks projects w/ many assets) | |
| ├── [email protected] (updating breaks projects w/ many assets) | |
| ├── [email protected] (latest) | |
| ├── [email protected] -> 1.1.0 (tested w/ project, mostly updates to underlying less which is bugfixes) | |
| ├── [email protected] -> 0.7.0 (further updating breaks projects w/ many assets) | |
| ├── [email protected]. (tested w/ project) | |
| ├── grunt-sails-linker@~0.9.6 (ours) | |
| ├── [email protected] -> 0.2.4 (tested w/ project) | |
| ├── [email protected] (latest) | |
| ├── include-all@~0.1.6 (ours) | |
| ├── [email protected] (upgrading breaks projects. would be worth fixing the issues w/ upgrading to 3.x, but leaving for now) | |
| ├── [email protected] -> ~0.2.1 (ours) | |
| ├── [email protected] (latest) | |
| ├── [email protected] -> 0.2.0 (commits look good) | |
| ├── [email protected] -> 0.3.0 (commits look good) | |
| ├── [email protected] -> 1.2.1 (adds more wurds) | |
| ├── [email protected] (latest) | |
| ├── [email protected] -> 1.0.1 (been using, but no tests--could use some tests) | |
| ├── reportback@~0.1.9 (ours) | |
| ├── sails-build-dictionary@~0.10.1 (ours) | |
| ├── sails-disk@~0.10.8 (ours) | |
| ├── sails-generate@~0.12.4 (ours) | |
| ├── sails-hook-sockets@~0.12.0 (ours) | |
| ├── sails-stringfile@~0.3.2 (ours) | |
| ├── sails-util@~0.10.6 (ours) | |
| ├── [email protected] -> 5.1.0 (been using 4.3.6, update is mostly about non-node usage and comments) | |
| ├── [email protected] (ours) | |
| ├── [email protected] (fine for us, update is for promise stuff) | |
| └── [email protected] (ours) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right- updating lodash or async is a good idea, but would be a breaking change. We could do it for 0.12