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
In workspace mode, it seems like synp tries to read all package.json files in the node_modules, even if they are not the main package.json file for the package. We're trying to convert yarn.lock to package-lock.json and one of our sub-dependencies is resolve package, which includes a bunch of invalid package.json files in their test suite. This causes the conversion to fail with Unexpected end of JSON input error.
Are you reporting a conversion error? Please include a link to yarn.lock / package-lock.json:
Cannot link to the whole yarn.lock, but the relevant parts are
I'm afraid this a side effect of how nmtree works. But we are experimenting on trees generation (depgraph, deptree, nmtree) without fs projections. The PoC is in early stages, but looks promising.
Issue description:
In workspace mode, it seems like synp tries to read all package.json files in the node_modules, even if they are not the main package.json file for the package. We're trying to convert yarn.lock to package-lock.json and one of our sub-dependencies is resolve package, which includes a bunch of invalid package.json files in their test suite. This causes the conversion to fail with
Unexpected end of JSON input
error.Are you reporting a conversion error? Please include a link to
yarn.lock
/package-lock.json
:Cannot link to the whole yarn.lock, but the relevant parts are
Are you reporting a conversion error? Please also include a link to your
package.json
:The text was updated successfully, but these errors were encountered: