0

My goal is to publish a custom Angular schematic package to my company's private npm registry for other devs to leverage. Here's what I've accomplished so far:

  • Created separate schematic project using schematic CLI.
  • Verified the schematic works locally in an Angular project via npm link.
  • Built and published the schematic project to the company registry.

When I try to npm install from the registry, I end up running into errors. First, there's a permissions warning on missing write access to the corresponding node_modules subfolder, and then npm eventually fails with ENOENT: No such file or directory for the same folder.

I'm unable to figure out what I missed. Could someone please point me in the right direction?

Thanks.

1 Answer 1

1

Removing node_modules addressed the issue. There must've been artifacts leftover from the previous link.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.