Unescape entries when we initially build our full package #1047
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.
Unfortunately, when we removed escaping in 1.7.0, while we removed it everywhere for our own code, we forgot about the input - when people build their NuGet packages, NuGet will still do the escaping nonsense. We need to un-escape our input file, which sucks out loud because we can't use 7-Zip there, but 😢
This bug is really bad because it breaks npm scoped packages, one of which is in the box in every electron-forge app.
Fixes #1044