Does anyone know how to make npm use a specific fork containing a bug fix while waiting for maintainer to merge a pull request? I was just going to point my package.json to this fork, like this: "svelte-material-ui": "https://github.com/vtpatrickeddy/svelte-material-ui.git#patch-1", but that doesn't work because the repo is a monorepo. And there doesn't appear to be a way to specify a subdirectory inside it, like: "@smui/textfield": "https://github.com/vtpatrickeddy/svelte-material-ui.git/packages/textarea#patch-1",

I pushed the build files & tested it in my environment so this should work as is.

I pushed a hotfix, based on v3.6.3 proposed by #2086 (comment) In package.json, under devDependencies, use: "svelte": "btakita/svelte#svelte-gh-2086-hotfix"

This is more a rhetoric question as this seems to be quite hard ;-) There is a long discussion about installing a subfolder of a repository and monorepos in general at the NPM Github issues (yarn misses this feature, too). The thing is that this makes it quite hard to report issues of your project as one can't test the current master easily. Do you recommend a way how to use the latest Github version?

GitHub Packages uses the native package tooling commands you're already familiar with to publish and install package versions.

The url also contains an optional refspec (#v0.0.1) that tells npm which branch, commit, or in this case tag you want to have checked out.

"neutrino-patch": "git+https://github.com/davidje13/neutrino-patch#semver:^1.0.1"

npm install --save git+https://github.com/davidje13/neutrino-patch#semver:^1.0.1

But what you absolutely should do is test your NPM package in its published format. Create some smoke tests that reside in the actual codebase, but are not part of the test suite.

libphonenumber

NPM was not and is still not designed to specifically be a node package manager. Yes it has a lot of useful features supporting node.js (some like node_modules is even hardcoded in node.js) but it actually doesn't care what language your software is written in. It is a package manager for your OS, just like apt and yum (or brew for you Mac users).

This is because it's not a node-specific package manager so what it installs could be a Python script or a shell script or a binary executable written in assembly.

I found adding a "prepare": "npm run build" to scripts fixed all my problems.

Update the package.json in your forked repo to add a postinstall element to scripts. In here, run whatever you need to get the compiled output (Preferred).

instead of prepublish, you'll need to use prepare, but this is otherwise as you'd expect.

prepare: Run both BEFORE the package is packed and published, on local npm install without any arguments, and when installing git dependencies

This is because it's not bundled at all, while the package expects an prebuilt version existing in dist.