Page MenuHomeSolus

Initial commit of lerna
ClosedPublic

Authored by theSoenke on Jan 5 2018, 10:29 PM.
Tags
None
Referenced Files
F11016479: D1889.diff
Sat, Aug 5, 6:11 PM
F11004097: D1889.diff
Mon, Jul 31, 10:32 PM
F10987107: D1889.diff
Mon, Jul 24, 4:20 AM
F10970704: D1889.id4476.diff
Fri, Jul 21, 3:48 AM
F10960049: D1889.diff
Tue, Jul 18, 9:18 AM
F10863726: D1889.diff
Jun 17 2023, 3:57 AM
F10833328: D1889.diff
Jun 6 2023, 6:52 PM
F10832894: D1889.diff
Jun 6 2023, 11:05 AM
Subscribers

Details

Summary

Dependency for D1785

Test Plan

Run lerna --version
Build insomnia package

Diff Detail

Branch
master
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

This revision is now accepted and ready to land.Jan 6 2018, 6:51 PM

Build failed.

error An unexpected error occurred: "https://registry.yarnpkg.com/pinkie-promise/-/pinkie-promise-2.0.1.tgz: Request failed \"404 Not Found\"".

Please create a new diff on https://dev.solus-project.com/source/lerna/repository/master/ with a patch to bump the pinkie-promise rel (can typically just be done with yarn upgrade pinkie-promise@version prior to yarn / yarn install).

Closed by commit R3943:e79f9769427f: Initial commit of lerna (authored by Sönke Behrendt <thesoenke@outlook.com>, committed by JoshStrobl). · Explain WhyJan 6 2018, 6:57 PM
This revision was automatically updated to reflect the committed changes.

I get the feeling the yarn registry currently has some issues. Upgrade to pinkie-promise 2.0.2 did not work for me.

yarn upgrade pinkie-promise@2.0.2
yarn upgrade v1.3.2
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/duplexer3/-/duplexer3-0.1.4.tgz: Request failed \"404 Not Found\"".

duplexer3 also can't be upgrade. Maybe we just have to wait a little bit until this gets solved

Curious if duplexer3 was affected as well, as per build log for mailspring.

Yep, was: This one package https://www.npmjs.com/package/duplexer3 was unavailable for close to 30 mins.

JoshStrobl added a subscriber: curantes.

@theSoenke and @alecbcs, I'll wait an hour or so until the dust settles and try republishing.

Edit: Sorry curantes for the ping. I need more coffee.

Yep, duplexer3 was also affected. Seems that the package has been hijacked. Might make sense to wait a little bit ;)

It wasn't hijacked, someone just published an alternative. Regardless, certainly gonna be waiting longer than an hour lol.