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
The current package.json has no version or name fields. These would be irrelevant in all cases, except that Yarn depends on them to be able to install the package locally from a specific branch, tag, or commit or even local folder. Thus, it is impossible to test local fixes from other contributors without silly workarounds like manually hacking package.json in the fork.
Hello @Swader can you give us a reproduction in what you want to achieve please. Actually the version of the global package is in packages/*package.json or in lerna.json.
Uh oh!
There was an error while loading. Please reload this page.
The current
package.json
has noversion
orname
fields. These would be irrelevant in all cases, except that Yarn depends on them to be able to install the package locally from a specific branch, tag, or commit or even local folder. Thus, it is impossible to test local fixes from other contributors without silly workarounds like manually hackingpackage.json
in the fork.Reference issue: yarnpkg/yarn#6195
If I'm using the wrong approach, please let me know of a better way to test things (specifically, I'm testing a bounty: https://gitcoin.co/issue/vuejs/vuepress/1613/3333)
The text was updated successfully, but these errors were encountered: