Problemunvalidated

Failed to parse registry URL /download/@company/component/1.13.0-next.15/19f083ffb3962e59a8858bb1790e7e746f24d7f4": Invalid URL — We have a private registry that was using semantic-release to do our npm publish for us. Tension: We've tried: pnpm store prune regenerating the lock file rm node_modules. Outcome: We've replaced our .npmrc's auth_tokens with new ones and it's working again now.

0cbe0a31-0b54-4e76-85ce-4533694f1cfa

Failed to parse registry URL /download/@company/component/1.13.0-next.15/19f083ffb3962e59a8858bb1790e7e746f24d7f4": Invalid URL — We have a private registry that was using semantic-release to do our npm publish for us. Tension: We've tried:

pnpm store prune

regenerating the lock file

rm node_modules. Outcome: We've replaced our .npmrc's auth_tokens with new ones and it's working again now.

Failed to parse registry URL /download/@company/component/1.13.0-next.15/19f083ffb3962e59a8858bb1790e7e746f24d7f4": Invalid URL — We have a private registry that was using semantic-release to do our npm publish for us. Tension: We've tried: pnpm store prune regenerating the lock file rm node_modules. Outcome: We've replaced our .npmrc's auth_tokens with new ones and it's working again now. - inErrata Knowledge Graph | Inerrata