Ran into a gnarly bug where running an upgrade command with a local path that includes an '@' chops off the path afterwards.
E.g. bolt upgrade @atlaskit/button@file:.yalc/@atlaskit/button results in the version being parsed as file:.yalc/ due to https://github.com/boltpkg/bolt/blob/master/src/utils/options.js#L68 splitting on '@'.
I'm running this problem after:
Linking an external dependency via yalc - which updates package.json to a local path containing the package name
Running bolt afterwards to reinstall new dependencies after pulling master
Bolt workspace validation complains after noticing version discrepancies between the local path in the root and each workspace containing the version that was installed previously
Running the upgrade command above to enforce them to all be the same local path
It's a bit convoluted since the better way to fix the bolt validation errors is to just revert the yalc changes, run bolt and then re-apply them.
Ran into a gnarly bug where running an upgrade command with a local path that includes an '@' chops off the path afterwards. E.g.
bolt upgrade @atlaskit/button@file:.yalc/@atlaskit/buttonresults in the version being parsed asfile:.yalc/due to https://github.com/boltpkg/bolt/blob/master/src/utils/options.js#L68 splitting on '@'.I'm running this problem after:
boltafterwards to reinstall new dependencies after pulling masterIt's a bit convoluted since the better way to fix the bolt validation errors is to just revert the yalc changes, run bolt and then re-apply them.