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 exe.js, nexe loads files and runs split('\n'), then compares lines. If the node source used is the git repo (maybe only on windows), the line endings in the .cc files are \r\n, and the subsequent line comparisons fail.
replacing
let lines = mainC.split('\n');
with
let lines = mainC.replace(/\r\n/g,'\n').split('\n');
and
var contentsSplit = contents.split('\n');
with
var contentsSplit = contents.replace(/\r\n/g,'\n').split('\n');
will make it work in all cases?
The text was updated successfully, but these errors were encountered:
i've modified my global git config ("core.autocrlf" is set to "input"), and will report if this helps. In the end, the build of direct GIT 6.9.1 (with autocrlf=auto) did not work for some reason; i'm wondering if there is something else (maybe on node build itself) which is line ending sensitive.....
in exe.js, nexe loads files and runs split('\n'), then compares lines. If the node source used is the git repo (maybe only on windows), the line endings in the .cc files are \r\n, and the subsequent line comparisons fail.
replacing
let lines = mainC.split('\n');
with
let lines = mainC.replace(/\r\n/g,'\n').split('\n');
and
var contentsSplit = contents.split('\n');
with
var contentsSplit = contents.replace(/\r\n/g,'\n').split('\n');
will make it work in all cases?
The text was updated successfully, but these errors were encountered: