As you can see the build command already throws an error.
But what is it?
Now files have changed (although) they shouldn't have since we haven't done any changes to the contents them selves.
git status
What has changed?
git diff ./products/SandboxApp.browser.js
As you can see it looks as if nothing changed, yet all the lines are marked as different what happned is that now what used to have two spaces now have four!
Even worst the generated files are invalid.
What is the expected result?
the files shouldn't change on successive npm run build
How to automate this bug report?
this issue is valid markdown and valid bash. In order to reproduce it just copy the raw markdown and do:
set -xeuo pipefail IFS=$'\n\t'
build creates invalid files on second run.
on consecutive runs of npm run build it generates invalid files. becaus the files have more spaces.
Steps to reproduce.
clean any previous build of this issue/script
Create a fresh install of jtree
As you can see nothing has changed:
Now let's swap the last two lines of projects.tree in order to trigger a rebuild.
Execute build again
As you can see the build command already throws an error.
But what is it?
Now files have changed (although) they shouldn't have since we haven't done any changes to the contents them selves.
What has changed?
As you can see it looks as if nothing changed, yet all the lines are marked as different what happned is that now what used to have two spaces now have four!
Even worst the generated files are invalid.
What is the expected result?
the files shouldn't change on successive npm run build
How to automate this bug report?
this issue is valid markdown and valid bash. In order to reproduce it just copy the raw markdown and do:
bash ./build_issue.md.sh