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 the comment for executeJs it is mentioned that if an escape character is emitted from the JS task to stdout, it will parse what immediately follows as JSON, which is great. However, many existing node modules (in my case, webpack) have a flag (like --json ) to toggle JSON output vs human readable output. These flags don't by default emit the character SBT JS Engine is looking for. Could you add a flag to SbtJsTask.executeJs to simply attempt to parse whatever the output of the script is in JSON? Could the parser also tolerate whatever whitespace / line-break settings are used to produce the JSON output?
My current workaround for this is to essentially wrap the Webpack CLI with another script which will emit the proper character and also remove all whitespace from the output of Webpack.
The text was updated successfully, but these errors were encountered:
That sounds reasonable. You mentioned webpack. I just Googled and saw two sbt-webpack plugins. Do you happen to be using either of them or how are you calling webpack?
In the comment for executeJs it is mentioned that if an escape character is emitted from the JS task to stdout, it will parse what immediately follows as JSON, which is great. However, many existing node modules (in my case,
webpack
) have a flag (like--json
) to toggle JSON output vs human readable output. These flags don't by default emit the character SBT JS Engine is looking for. Could you add a flag to SbtJsTask.executeJs to simply attempt to parse whatever the output of the script is in JSON? Could the parser also tolerate whatever whitespace / line-break settings are used to produce the JSON output?My current workaround for this is to essentially wrap the Webpack CLI with another script which will emit the proper character and also remove all whitespace from the output of Webpack.
The text was updated successfully, but these errors were encountered: