Installing private packages that are not hosted on the public npmjs registry

[reviewher]

Modules are currently tied to the public npmjs registry. The search bar searches the public registry to add modules. There is no way to side-load modules into the fiddle.

Ideally there would be a package.json-esque way to control the npm resolution process.

If that is not desirable, one workaround is to specify paths to tarballs downloaded with npm pack $PACKAGE_NAME

[BhinbahadurUK]

Add Always configure add all functions UK Bhinbahadur

…

On Mon, 07 Nov 2022, 21:02 reviewher, ***@***.***> wrote: Modules are currently tied to the public npmjs registry. The search bar searches the public registry to add modules. There is no way to side-load modules into the fiddle. Ideally there would be a package.json-esque way to control the npm resolution process. If that is not desirable, one workaround is to specify paths to tarballs downloaded with npm pack $PACKAGE_NAME — Reply to this email directly, view it on GitHub <#1205>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEXF3X3AYSDKQF3IFNC5LFTWHFG35ANCNFSM6AAAAAARZQE4EA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>