question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

changeset publish is failed, Received 404 for npm info

See original GitHub issue

Affected Packages

@mercur1/hooks @mercur1/ui @mercur1/request @mercur1/ui-pro @mercur1/tokens @mercur1/directives @mercur1/utils

Problem

  1. execute pnpm changeset:gen to create changeset.
  2. git add . && pnpm commit && git push
  3. execute github action release.yml

You can see https://github.com/casta-fe/mercury-monorepo/actions/runs/3313242853/jobs/5470954044#step:11:14

Proposed solution

Hope pnpm exec changeset publish is success, and publish packages

When i publish first time, this always return E404.

// cli.esm.js

// ...

let result = await spawn$1("npm", ["info", packageJson.name, "--registry", getCorrectRegistry(packageJson), "--json"]); 

//...

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:5

github_iconTop GitHub Comments

1reaction
i7eocommented, Oct 25, 2022

Hi @Ethan-Arrowood . I resolve this mistake.

In my case, i install my sub package into other sub package devDependencies. When i put these to dependencies, mistake disappear. I don’t know what happened🥱.

I can give you a few suggestions:

  • Check for "private": true package, add "version": "0.0.0"
  • Put interdependent packages under dependencies instead of devDependencies
1reaction
i7eocommented, Oct 25, 2022

I created these @mercur1/hooks @mercur1/ui @mercur1/request @mercur1/ui-pro @mercur1/tokens @mercur1/directives @mercur1/utils manually.

Then i trigger GitHub Action release.yml, report errors. see https://github.com/casta-fe/mercury-monorepo/actions/runs/3313419924/jobs/5471372831#step:11:17

This confused me and I really didn’t know what to do. Can u look this? @Andarist @Noviny

Read more comments on GitHub >

github_iconTop Results From Across the Web

Getting 404 when attempting to publish new package to NPM
When i try to publish in console by login with normal username gave me this error. publish Failed PUT 404 npm ERR! code...
Read more >
404 Unable to identify proxy for host: <virtual host name> and url
This error means that Edge could not find the API proxy for the specified virtual host and path. Error Message. You will get...
Read more >
Yarn publish does not work (#121668) · Issues - GitLab
A yarn publish fails with a 404 when attempting to publish a package to the NPM registry. This looks it may be more...
Read more >
How to troubleshoot NPM problems - JFrog
Relevant versions: This information pertains to Artifactory versions 6.X and above. The npm client is used by many application pipelines to ...
Read more >
Top 10 Serverless Deployment Errors (and How to Fix Them)
If you see this error, check that the needed parameter is available in the environment you're trying to deploy to, and add it...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found