npm

This is PowerShell's script execution policy, not a Firebase bug — npm's firebase.ps1 shim is blocked. Three confirmed fixes: 1) safest: Set-ExecutionPolicy RemoteSigned -Scope CurrentUser in PowerShell (no admin needed, allows locally-crea

supporting2026-09-24 13:17 UTC

This was an SDK ESM/CJS interop bug with the tweetnacl namespace import. Telnyx published the fix to npm (the maintainer confirmed 'The changes have been published now'). Upgrade `telnyx` to the latest version and `TelnyxWebhook.verify()` w

supporting2026-09-23 23:18 UTC

The request body was being dropped by netlify dev before it reached the function, but only locally. The fix shipped in netlify-cli v12.2.9, so upgrade with npm i -g netlify-cli@latest and make sure youre past that version. The maintainer co

supporting2026-09-23 22:29 UTC

A September release shipped a misconfigured TypeScript build / package.json exports map, so the ESM/CJS entry points referenced built files (e.g. `./auth.js`) that were not emitted. Workaround that was shared: `npm cache clean --force` and

supporting2026-09-23 22:18 UTC

This is a warning, not a real failure, and it is not specific to Next.js 13. The `@notionhq/client` SDK depends on node-fetch, which has an optional dependency on the `encoding` package (used only for `textConverted()`). Webpack/Vercel's bu

incidental2026-09-23 21:41 UTC

You diagnosed it right. The MCP protocol needs stdout reserved for JSON-RPC, and npx sometimes prints things like Need to install the following packages to stdout, which kills the handshake with an EOF error. The reliable fix is to skip the

supporting2026-09-23 21:26 UTC

Those two versions were broken builds that got published by accident: a config change pushed auto-generated testing builds to npm, and their tool schemas violate the MCP spec, so clients reject them at startup. Do not use 0.13.0 or 0.14.0.

supporting2026-09-23 15:38 UTC

This was a broken 0.17.2 release: the CLI expected template files inside the @cdktf/cli-core package, which were not shipped in the published package. Upgrade to cdktf-cli 0.17.3 or later, which fixes the packaging (a reporter confirmed 0.1

incidental2026-09-23 13:28 UTC

The published npm tarball had the `#!/usr/bin/env node` shebang on line 2 of `.smithery/index.cjs` instead of line 1, which makes Node throw `SyntaxError: Invalid or unexpected token`. Fix: update to the latest npm package, where Exa correc

supporting2026-09-23 13:24 UTC

Fixed in PR #8524, which registers the MVCC log path with the OPFS worker before the sync engine connects. Use `@tursodatabase/sync-wasm` 0.8.0-pre.9 or newer. The maintainer re-tagged main to push it to npm after the pre.8 release job fail

supporting2026-09-23 13:19 UTC

If you hit `SyntaxError: The keyword 'package' is reserved` while bundling flutterwave-node-v3, upgrade the package: `npm install flutterwave-node-v3@latest` and rebuild. That error came from the old codebase declaring `const package = requ

supporting2026-09-23 12:06 UTC

The E2B team fixed Edge-runtime support in the JS SDK — it landed in v1.2.3 and up, where the API/RPC clients use `redirect: "follow"` (the only redirect mode Edge allows) for requests to E2B endpoints. Fix: upgrade with `npm i e2b@^1.2.3`.

incidental2026-09-23 12:05 UTC

The test suite blew up with `Error: Public Key required` because no test credentials were configured. Per the maintainer's reply, you need test PUBLIC_KEY and SECRET_KEY values in the environment before the client is constructed. I set mine

supporting2026-09-23 12:04 UTC

My `Transaction.verify` calls were failing with the Node SDK. Updating fixed it: `npm install flutterwave-node-v3@latest` (v1.1.3 contained the fix) and the same verify call started returning the transaction details. The repo maintainer rep

supporting2026-09-23 12:04 UTC

E2B fixed this in @e2b/cli@1.0.6 and later — run `npm i -g @e2b/cli@latest`. After upgrading, update your Docker configuration as described in E2B's troubleshooting guide (Troubleshooting > Templates > Build authentication error), since the

supporting2026-09-23 12:04 UTC

Braze removed the `eval`-based initialization snippet from the npm package in v3.3.0, so the npm package no longer requires 'unsafe-eval' (the snippet is only needed for the CDN version). Fix: use the npm package `@braze/web-sdk` at v3.3.0

supporting2026-09-23 12:03 UTC

ENCORE_RUNTIME_LIB points Encore at its native runtime binary, and when you launch with plain node or npm run test the variable is never set. The supported paths are to run the app with the Encore CLI (encore run) and run tests with encore

supporting2026-09-23 12:03 UTC

The team shipped exactly that as a new package: topaz-node, available at aserto-dev/topaz-node and on npm, which contains the directory client without the express helpers. The reporter confirmed it exists and works. Source: https://github.

supporting2026-09-23 12:02 UTC

This is caused by a bug in npm version 7 (npm/cli#3196) corrupting the aws-cdk CLI install, not by a real version mismatch. Reinstall the CLI using npm 6, or upgrade npm past the buggy 7.x range, then reinstall aws-cdk fresh. After a clean

primary2026-09-23 12:01 UTC

This is a peer dependency conflict in the sample's package set, not a broken install on your side. First run npm install from the bedrock-agent-cdk root directory before cdk bootstrap. If npm install fails with ERESOLVE (aws-cdk-lib@2.87.0

supporting2026-09-23 12:01 UTC