You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`Package ${params.pkg.name} depends on ${found.pkg.name} but ${found.pkg.name} is not published, and no target version was set for publishing now. Did you opt to skip publishing ${found.pkg.name}? If so, please re-run and make sure to publish ${found.pkg.name}. You can't publish ${params.pkg.name} until you do that.`,
483
+
`Package ${params.pkg.name} depends on ${foundDep.pkg.name} but ${foundDep.pkg.name} is not published, and no target version was set for publishing now. Did you opt to skip publishing ${foundDep.pkg.name}? If so, please re-run and make sure to publish ${foundDep.pkg.name}. You can't publish ${params.pkg.name} until you do that.`,
@@ -670,7 +675,7 @@ type PackageJson = import('type-fest').PackageJson & {
670
675
* not an official package.json field, but there is a library that does something similar to this: https://github.com/Metnew/git-hash-package
671
676
* having git.sha point to a commit hash seems pretty useful to me, even if it's not standard.
672
677
* tagging versions in git is still a good best practice but there are many different ways, e.g. `1.2.3` vs `v1.2.3` vs `[email protected]` vs `[email protected]`
673
-
* plus, that's only useful in going from git -> npm, not npm -> git.
678
+
* plus, that's only useful in going from git to npm, not npm to git.
0 commit comments