golem-add-npm-package

Add npm package dependencies to TypeScript Golem projects.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Rust-soham/golem-claw --skill golem-add-npm-package-rust-soham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem-add-npm-package
Source: https://github.com/Rust-soham/golem-claw/tree/main/packages/golem/.agents/skills/golem-add-npm-package
Command: npx skills add https://github.com/Rust-soham/golem-claw --skill golem-add-npm-package-rust-soham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of adding a required npm package dependency to a TypeScript Golem project while avoiding runtime incompatibilities in the QuickJS (WASM) environment.

Core Features & Use Cases

  • Install new dependencies: Adds either production dependencies or dev-only dependencies to the project’s package.json via npm install.
  • Ensures build verification: Uses golem build to validate that the package works with the Golem Rollup/TypeScript bundling pipeline.
  • Prevents QuickJS runtime breakage: Guides you away from native Node.js C++ addons and known stubbed modules that fail inside QuickJS.

Quick Start

Ask the assistant to add the npm package dependency named "some-library" to your Golem TypeScript project, then verify it using golem build.

Frequently Asked Questions about golem-add-npm-package

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add an npm package to a TypeScript Golem project?

To add an npm package to a TypeScript Golem project, install the dependency from the project root using npm install, then verify compatibility by running golem build to ensure it works with the Rollup bundling pipeline.

What npm packages are incompatible with the Golem QuickJS runtime?

Packages relying on native Node.js C++ addons are incompatible with the Golem QuickJS WASM runtime. You should also avoid known stubbed modules to prevent runtime breakage during execution in the Golem environment.

Why does golem build fail after installing a new npm dependency?

Golem build fails after adding an npm dependency when the package includes native Node.js addons or stubbed modules that cannot compile or run inside the QuickJS WASM environment, breaking the TypeScript Rollup bundling process.

Can I use native Node.js addons in a Golem TypeScript component?

You cannot use native Node.js addons in a Golem TypeScript component because the QuickJS WASM runtime does not support C++ native extensions, causing build verification and runtime failures.

What is the best way to manage runtime compatibility for npm dependencies in Golem?

The best way to manage npm dependency compatibility in Golem is to install packages via npm, verify them using golem build, and strictly avoid native Node.js addons and known stubbed modules that break the QuickJS WASM runtime.