-
### Description
It would be nice if iD published its own npm package.
### Screenshots
_No response_
-
Hello,
I really appreciate your library and all the work you have put into this project.
I use your project by downloading it from the npm registry, however the last publish on npm was two year…
-
This would allow us to update the modules, as well as the vscode extension, immediately, rather than having to wait for a release.
Could potentially use GitHub's own NPM registry.
-
there is a `package.json` with a package name: `oas-schemas` but this package doesn't exist in `npmjs.com` ...
-
Dear Jared Hanson,
Hope this finds you well, recently I wish to deploy my new framework called pocket into the npm registry, but I found that this repo has been occupied for the npm.
For my pock…
-
Hi, nice implementation.
I did not yet find another library that delivers the heroicons as webcomponents. And since we use these already it would be very beneficial to install them from NPM.
-
### Describe the feature or enhancement
Hi there 👋
Integrating umami with JS projects that use a bundler would be more convenient with a published library. Especially when using TypeScript, since…
-
Is there any plan to publish these packages to NPM and the Construct Catalog? I would like to manage everything through version controlled TypeScript code if possible. Am I thinking about this wrong?
-
Currently, the NPM packages are published to an org called `knative-extensions`: https://www.npmjs.com/package/@knative-extensions/plugin-knative-event-mesh-backend
This org is owned by me and …
-
Hey, thanks for the package. Could you please publish it on npm? Cloning and building it manually seems weird.