This would ~only apply the newline option when concatenating js files and leave css files alone~ ignore newline semicolon for css files. It turns out css files do not need this option. If they do, then we can come up with another solution. I want to make sure that is needed first though.
Coverage increased (+0.01%) to 98.16% when pulling a6fa6535cf83662d58c6cbb6a40143086bd4a85f on newline into b06ecc5c76ba5dc26e631f1f88d5fccecdfeb42b on master.
Coverage increased (+0.01%) to 98.16% when pulling a6fa6535cf83662d58c6cbb6a40143086bd4a85f on newline into b06ecc5c76ba5dc26e631f1f88d5fccecdfeb42b on master.
Coverage increased (+0.04%) to 98.193% when pulling 83c749ae580bf151fc06a6e5e4c335e1335afe81 on newline into b06ecc5c76ba5dc26e631f1f88d5fccecdfeb42b on master.
Proposed fix to #241 and #248.
This would ~only apply the newline option when concatenating js files and leave css files alone~ ignore newline semicolon for css files. It turns out css files do not need this option. If they do, then we can come up with another solution. I want to make sure that is needed first though.