-
The built artifacts of the wasm version are not currently available. Publishing them as a wasm package on npm or including them in GitHub releases would be nice.
-
I would like to use this project in a Node.js package with version tracking like changes in new version and a feature to save user data permanently to local project.
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### This issue exists in the latest npm version
- [X] I am using the latest npm
### Current Behavior
When you ru…
-
Hi Econia Labs team, I would like to request that you consider publishing your SDK to the npm registry.
Thanks.
-
Please publish 0.5.0 on npm. It's still on 0.4.1: https://www.npmjs.com/package/@libsql/kysely-libsql
-
[Provenance statements](https://github.blog/security/supply-chain-security/introducing-npm-package-provenance/) are a nice way to increase confidence in the integrity of published npm packages. It…
-
Sorry if I'm dense -- couldn't find it :sweat_smile:
-
This grammar is not published on npm, although it is properly working (when #40 is merged).
Can this grammar be published there?
-
The `deploy` directory should be published to NPM to support other applications that want to deploy htsget-rs using CDK.
A few changes/considerations for the current CDK stack:
- [x] The stack sho…
-
It would be awesome if this package was published on NPM so it could be easily accessible via `bun install adminjs-drizzle`
currently i have the package as git dependency and i have to build in eve…