Skip to content

docs: forbid in-vault npm install (crash-loops Obsidian sync)#17

Open
agiacalone wants to merge 1 commit into
mainfrom
fix/no-npm-install-in-vault
Open

docs: forbid in-vault npm install (crash-loops Obsidian sync)#17
agiacalone wants to merge 1 commit into
mainfrom
fix/no-npm-install-in-vault

Conversation

@agiacalone

Copy link
Copy Markdown
Owner

When this skill is checked out inside an Obsidian vault, a bare npm install drops node_modules/ into the vault. Its thousands of nested dirs exhaust the inotify watch budget and crash-loop the Obsidian sync daemon (and spawn sync-conflict dup folders).

Rewrites SKILL.md, CLAUDE.md, and README.md to forbid in-vault npm install and document installing at the vault parent via --prefix (Node resolves the parent node_modules upward automatically). Post-skills-move, deps simply live in this repo normally.

Docs-only; no code changes.

🤖 Generated with Claude Code

The skill is checked out inside the Obsidian vault, so a bare 'npm install'
creates node_modules in the vault. Its thousands of nested dirs exhaust the
inotify watch budget and crash-loop the Obsidian sync daemon. Deps belong at
the vault parent (or, post-reversal, the skill's own git repo), where Node's
upward module resolution finds them automatically.

Rewrites SKILL.md, CLAUDE.md, README.md to forbid in-vault installs.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014bMW9YHzZzP3FLK95PW64Q
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant