[Feature Request] Programmatic usage (JavaScript SDK)

[SukkaW]

No description provided.

[DonMiller9294]

I would like to help you out, could you give a description?

[SukkaW]

I would like to help you out, could you give a description?

Thanks!

I have not come up with an API design yet, but the package should work like this:

• Can be installed through @nolyfill/sdk.
• Given a project path:
  • It should be able to detect the preferred package manager
  • It should be able to build the dependency tree of the current project
  • It should be able to detect the nolyfill alternatives that can be applied to the current project
• Currently, the nolyfill CLI (the nolyfill package) implements all the mentioned logics above. They should be moved to @nolyfill/sdk, and the nolyfill CLI will use the @nolyfill/sdk as a dependency.

[nonzzz]

I would like to help you out, could you give a description?

Thanks!

I have not come up with an API design yet, but the package should work like this:

• Can be installed through @nolyfill/sdk.

• Given a project path:

  • It should be able to detect the preferred package manager
  • It should be able to build the dependency tree of the current project
  • It should be able to detect the nolyfill alternatives that can be applied to the current project

• Currently, the nolyfill CLI (the nolyfill package) implements all the mentioned logics above. They should be moved to @nolyfill/sdk, and the nolyfill CLI will use the @nolyfill/sdk as a dependency.

Currently, nolyfill CLI has implements all the logics ( perhaps the SDK might a lower abstraction?)
But before implement the SDK. I'm more concerned with things like npm update and pnpm,yarn dependencies tree can be processed correctly

[JounQin]

I think we should also have @nolyfill/core or @nolyfill/data for reusing in other projects like https://github.com/wojtekmaj/yarn-plugin-nolyfill