synp: Could not find parent dir!
Issue description:
Bet you didn’t expect to get an issue report 10 minutes after releasing a new version, but the new release seems to break something in my workflow. I get the following error: Could not find parent dir!, while everything worked fine one hour ago.
Are you reporting a conversion error? Please include a link to yarn.lock / package-lock.json:
Are you reporting a conversion error? Please also include a link to your package.json:
See attached *.zip
EDIT: FYI I ran npx synp --source-file yarn.lock
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (4 by maintainers)
Commits related to this issue
- fix: adapt parentPackagePath resolver to relative paths closes #46 — committed to imsnif/synp by antongolub 4 years ago
- fix: parentPackagePath resolver (#47) * refactor: separate workspace utils * fix: adapt parentPackagePath resolver to relative paths closes #46 * fix(lockfileV2): add some missed relative pa... — committed to imsnif/synp by antongolub 4 years ago
- chore(release): 1.0.0 [skip ci] # 1.0.0 (2020-08-31) ### Bug Fixes * better cli errors ([1e05ade](https://github.com/imsnif/synp/commit/1e05adeeb62f5141e7e05ad46c9000634f484703)) * check node_modul... — committed to imsnif/synp by antongolub 4 years ago
- chore(release): 1.0.0 [skip ci] # 1.0.0 (2020-08-31) ### Bug Fixes * better cli errors ([1e05ade](https://github.com/imsnif/synp/commit/1e05adeeb62f5141e7e05ad46c9000634f484703)) * check node_modul... — committed to imsnif/synp by antongolub 4 years ago
Hi there, @imsnif @LuudJanssen
I’ll look for what could break. Sorry for the inconvenience.
@alexiusp, @LuudJanssen,
Everything should be fixed in v1.8.2. If not, feel free to open another one issue.
Sorry for losing the track. In version 1.8.2 everything works as expected. Thank you!