Remove BOM from package.json #28
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you, I'd like to merge your pull request into branch 2.1.x instead of master. Could you change the target merging branch accordingly? |
|
new pull request for branch v2.1.x sent as #29 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The BOM (Byte Order Marker) at the beginning of the package.json is not fully supported by
npmand other tools. Webpack fails with an error:BowerComponents/lightcase/package.json (directory description file): SyntaxError: Unexpected token, npm itself has problems withinstall --saveandupdate --save.Depending on which way you look at the standards JSON with UTF-8 BOM isn't valid json either.
Since none of the other files in the repository have a BOM, remove it to avoid problems.