Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

inline <script> and <style> tags should get processed by Greenwood standard resource plugins #534

Open
1 of 5 tasks
thescientist13 opened this issue Apr 11, 2021 · 0 comments
Labels
CLI enhancement Improve something existing (e.g. no docs, new APIs, etc)
Milestone

Comments

@thescientist13
Copy link
Member

thescientist13 commented Apr 11, 2021

Type of Change

  • New Feature Request
  • Documentation / Website
  • Improvement / Suggestion
  • Bug
  • Other (please clarify below)

Summary

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.

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;
  }
}

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.

@thescientist13 thescientist13 added enhancement Improve something existing (e.g. no docs, new APIs, etc) CLI labels Apr 11, 2021
@thescientist13 thescientist13 added this to the Post 1.0 milestone Apr 11, 2021
@thescientist13 thescientist13 removed this from the Post 1.0 milestone Mar 15, 2022
@thescientist13 thescientist13 added this to the 1.0 milestone Nov 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLI enhancement Improve something existing (e.g. no docs, new APIs, etc)
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant