-
Notifications
You must be signed in to change notification settings - Fork 918
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
Prevent pipeline.js from moving standaline scripts on build #1897
Conversation
@samtstern snuck in a couple more fixed if you can PTAL again |
if (isLocalFirepit) { | ||
echo("Using local firepit for testing..."); | ||
mkdir("firepit"); | ||
rm("-rf", path.join(__dirname, "../vendor/node_modules")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why dont you need to rm
these files anymore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This whole step was only used when the --local
flag was used which was only helpful when this script made a distinction between local
(i.e. build from current directory) and remote
(build from HEAD on Github). Since this script no longer support the remote flow and now does all work in a temp directory, we can simplify this and allow the cleaning of the temp dir to do this removal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok makes sense. Can you add a comment to the top of this file explaining what flags are accepted? Since it just examines argv
at different times it's kind of hard to know.
There was a minor bug in the
firepit-builder
which made local development harder because it would remove thestandalone/
folder instead of just copying it to the right place.