Closed jordwalke closed 7 years ago
It's not implemented for opam fetcher — working on it.
Should be fixed in esy@0.0.24
. It's pretty significant rewrite of opam resolver/fetcher within the esy install so I've released it under next
tag for now:
npm i -g esy@next
Let's test!
Will test! Hope it wasn't too much work.
Seems to be working great! There isn't a way to really force esy
to use offline because esy install
doesn't forward args to yarn right now, but I disconnected wifi to try it and it worked very well. Pretty cool that we have this offline feature - it's really important for companies that need to perform builds offline in an isolated environment.
esy install doesn't forward args to yarn right now
yeah, going to fix this and also expose esy add
and few others.
Closing this issue for now.
Since moving ocaml compiler to
npm
, now the offline cache is no longer corrupt, but I noticed the offline cache doesn't include@opam
packages.This might be a quick/obvious fix, or it might be more involved. If it's more involved, I think we can deprioritized it and I can just find some other workaround to getting offline checkins of dependencies. Curious to hear @andreypopp's thoughts:
Here's my project's
.yarnrc
:Here's a sample section of my newly generated
yarn.lock
, which shows something interesting: Theresolved
field doesn't have a full url for@opam
packages, but does for npm ones.Here's the contents of the
npm-packages-offline-cache
directory: