Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix crashes when path to prototype contains spaces #1841

Merged
merged 2 commits into from
Dec 8, 2022
Merged

Conversation

lfdebrux
Copy link
Member

@lfdebrux lfdebrux commented Dec 6, 2022

Closes #1840

We had a user unable to use the migration script because the path to their prototype included spaces. Fix this by not spawning via the shell in bin/cli; we don't need to, and this way we don't need to worry about escaping command line arguments.

We had a user unable to use the migration script because the path to
their prototype included spaces. Fix this by not `spawn`ing via the
shell in `bin/cli`; we don't need to, and this way we don't need to
worry about escaping command line arguments.
On Windows using `spawn('npm', ...)` raises an ENOENT error, because of
PATHEXT issues. Using [cross-spawn] fixes this.

[cross-spawn]: https://www.npmjs.com/package/cross-spawn
@lfdebrux lfdebrux merged commit ef06d5a into main Dec 8, 2022
@lfdebrux lfdebrux deleted the ldeb-fix-1840 branch December 8, 2022 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migration script crashes if current working directory has spaces in path
2 participants