Type of Change
Summary
Currently HTML transformation is limited to just handling HTML and markdown. Which means that if you have something like this in your template
<style>
p {
& span {
color: red;
}
}
</style>It will not get processed by PostCSS, for example. Similar thing would happen if say you used TypeScript in an inline <script> tag.
Details
For this to work, Greenwood's HTML Resource plugin would have to scan for those tags and figure out how to process them and then stick the transformed JS / CSS back into the HTML.
This same action would need to be done in Rollup as well.
EDIT: not sure if this still applies anymore since i think this might work now, but worth double checking as we get closer to the 1.0 release.
Type of Change
Summary
Currently HTML transformation is limited to just handling HTML and markdown. Which means that if you have something like this in your template
It will not get processed by PostCSS, for example. Similar thing would happen if say you used TypeScript in an inline
<script>tag.Details
For this to work, Greenwood's HTML Resource plugin would have to scan for those tags and figure out how to process them and then stick the transformed JS / CSS back into the HTML.
This same action would need to be done in Rollup as well.