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
When building Kotlin code in a directory with spaces, Parcel errors out with [path to file before space] is not recognized as an internal or external command, operable program or batch file (on Windows). It is expected that this error will happen on other operating systems as well.
Parcel errors, saying that the directory before any spaces is not recognised as an internal or external command.
💁 Possible Solution
The bug is probably caused by there not being quotes around the path containing the Kotlin compiler, meaning that the OS interprets the space as separating the command and an argument.
🔦 Context
This issue came up while attempting to fix another bug, where I created a folder to test in that had a space in its name. When attempting to run Parcel, it came up with this error, so I had to remove any spaces from the path, and then it worked.
🌍 Your Environment
Software
Version(s)
Parcel
1.11.0
Node
11.1.0
npm/Yarn
1.12.1
Operating System
Windows 10 (1809)
The text was updated successfully, but these errors were encountered:
This appears to be an issue in Node - kotlinc-js-api calls child_process.spawn, which doesn't seem to work when both arguments and the path have spaces (nodejs/node#7367).
🐛 bug report
When building Kotlin code in a directory with spaces, Parcel errors out with
[path to file before space] is not recognized as an internal or external command, operable program or batch file
(on Windows). It is expected that this error will happen on other operating systems as well.🎛 Configuration (.babelrc, package.json, cli command)
package.json:
CLI command:
npx parcel src/*.html
File structure:
🤔 Expected Behavior
Everything should compile as usual.
😯 Current Behavior
Parcel errors, saying that the directory before any spaces is not recognised as an internal or external command.
💁 Possible Solution
The bug is probably caused by there not being quotes around the path containing the Kotlin compiler, meaning that the OS interprets the space as separating the command and an argument.
🔦 Context
This issue came up while attempting to fix another bug, where I created a folder to test in that had a space in its name. When attempting to run Parcel, it came up with this error, so I had to remove any spaces from the path, and then it worked.
🌍 Your Environment
The text was updated successfully, but these errors were encountered: