'\n' in token output files causing issues in Windows #8350
Labels
4 - verified
Issues that have been released and confirmed resolved.
bug
Bug reports for broken functionality. Issues should include a reproduction of the bug.
Calcite (dev)
Issues logged by Calcite developers.
calcite-design-tokens
Issues specific to the @esri/calcite-design-tokens package.
estimate - 3
A day or two of work, likely requires updates to tests.
impact - p1 - need for current milestone
User set priority impact status of p1 - need for current milestone
p - high
Issue should be addressed in the current milestone, impacts component or core functionality
Milestone
Check existing issues
Actual Behavior
'\n' is written into platform output in tokens
Expected Behavior
tokens transformer should use npm
os.EOL
orPrettier.format()
Reproduction Sample
N/a
Reproduction Steps
Reproduction Version
2.0
Relevant Info
Originally brought up by Ben in #8344 (review)
Regression?
No response
Priority impact
p1 - need for current milestone
Impact
Blocking usage of token output files on Windows machines
Calcite package
Esri team
Calcite (dev)
The text was updated successfully, but these errors were encountered: