-
Notifications
You must be signed in to change notification settings - Fork 1
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
When file has a shebang, it should be kept intact (just like the BOM prefix) #5
Open
GerHobbelt opened this issue
Aug 8, 2020
· 1 comment
· May be fixed by #6 or hemanth/node-prepend-file#16
Open
When file has a shebang, it should be kept intact (just like the BOM prefix) #5
GerHobbelt opened this issue
Aug 8, 2020
· 1 comment
· May be fixed by #6 or hemanth/node-prepend-file#16
Comments
GerHobbelt
added a commit
to GerHobbelt/node-prepend-to-js-file
that referenced
this issue
Aug 8, 2020
…g, IFF the file has any. This fixes silesky/prepend-header#5
GerHobbelt
added a commit
to GerHobbelt/node-prepend-to-js-file
that referenced
this issue
Aug 8, 2020
- clean up *before* rather than *after*: we want to *start* clean, if we leave a bit of stuff for post-test scrutiny that's okay. Anyway, had a couple of nasty surprises by crashing tests and the *after* code not working, anyway.
GerHobbelt
added a commit
to GerHobbelt/prepend-header
that referenced
this issue
Aug 8, 2020
…stead of prepend-file.
GerHobbelt
added a commit
to GerHobbelt/prepend-header
that referenced
this issue
Aug 8, 2020
…stead of prepend-file. # Conflicts: # package.json
This was referenced Aug 8, 2020
BTW: took the second route instead of the first as I consider code duplication far worse than a fork + augment edit. The fix in the prepend-to-je-file has been tested there: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Example:
should become
when appending the text
Notes
The text was updated successfully, but these errors were encountered: