-
On initial install of this package and subsequent `npm update` runs, the following errors occur:
The `--…
-
**Describe the bug**
I have an error of npm version mismatch while building wasm example.
"ERROR: npm v10.4.0 is known not to run on Node.js v14.21.3. This version of npm supports the following n…
-
I downloaded the latest code and run "npm i" and I'm getting errors.
The main problem seems to be with node-gyp when it tries to build the pgsql-parser package. It throws an error (MSB8066) relate…
dlado updated
16 hours ago
-
Like we manually do for @duckdb/duckdb-wasm, it’d be nice if you could control the default version for packages, and perhaps the default entry. (But perhaps this is unnecessary since you can use a pac…
-
* [x] Update CircleCI orb image/node version to latest
* [x] Clean up e2e deploy logic - deploy job name for `develop` is misleading - we deploy even if e2e tests fail, this step should reflect th…
-
Hey,
Would it be possible to publish the older versions to the NPM registry?
There are probably more reasons others would like it on the registry, like being able to use it in something like [un…
-
Hello,
I'm one of the maintainers of [Soldeer](https://soldeer.xyz/project/solmate), the first package manager for solidity, currently integrated into foundry.
I've been asked if i am able to push …
-
### What is the problem this feature would solve?
If version needs to be update in package.json, npm version patch | minor | major can bump it for us, Very helpful in ci environments and for publis…
-
request update npm@fabricio-191/valve-server-query,this version too old
-
**Describe the bug**
Installing a specific version of an npm package freezes in GitHub Actions (`runs-on: ubuntu-latest`).
**To Reproduce**
Use the `jdx/mise-action` in GitHub Actions with `"npm:…