search

jordwalke / esy-issues

Easy ISSUES
MIT License
49 stars 5 forks source link

[HIGH PRI] Create version of opam file format parser that can be compiled to JS using BuckleScript. #90

Closed jordwalke closed 5 years ago

jordwalke commented 7 years ago

Having the ability to parse opam files directly from JS would allow us to clone opam repos and then build them locally easily without having to create opam switches etc.

Old text:

As a follow up to this issue, now that esy can be used as an npm dependency to perform postinstall builds, we need a lighter weight version of esy to be built that doesn't pull in all of yarn's dependencies. Right now npm esy is the total CLI. We should split it into two packages.

Either:

  • esybuild (the smaller builder) and esy (the cli) or
  • esy(the smaller builder) and esy-cli (the cli).

The smaller builder has no install capabilities and so needs nothing related to yarn. It assumes all packages have already been converted over to pure npm and pushed somewhere as pure npm.

wokalski commented 7 years ago

It assumes all packages have already been converted over to pure npm and pushed somewhere as pure npm.

Does this mean that it depends on #81? If yes, does it depend on that issue because esy uses some opam packages and that way esybuild could have them in its package.json?

wokalski commented 7 years ago

For anyone working on this:

I think they actually can be worked on in parallel, but before there's a dependency there before we can actually roll out the npm packages, yeah.

jordwalke commented 7 years ago

Repurposing this github issue.

kazcw commented 5 years ago

Is this addressed by jordwalke/esy-issues#98?

andreypopp commented 5 years ago

Originally by https://github.com/esy-ocaml/esy-opam but now this is abandoned as we ported esy to native — we use opam-* libs as is from opam now.

kazcw commented 5 years ago

Here is a BuckleScript builder for the current version of opam-file-format: kazcw/opam-file-format-bs. I'm not sure what else is needed.

kazcw commented 5 years ago

Maybe I'm interpreting "parser" too narrowly. Is this bug for the whole opam-to-npm converter discussed in #81?

wokalski commented 5 years ago

@kazcw this issue is obsolete because esy has moved on from compiling to JS.

jordwalke commented 5 years ago

Yes, thanks for the reminder. I'll close this. In fact most of the issues are in esy repo now.