PHP did the markup and server code mixing 20 years ago and collectively decided its a bad idea as it becomes unmaintanable pretty fast.
Now that gets further complicated by also mixing with frontend-stack complexity...
Can somebody explain to me why that is a good idea now?
@adamwathan I like size. It's less obvious than m and p, because it's (r will be) new to CSS. And it's consistent with spelling out "right" and "left" (`right-0` etc) in Tailwind.
@nullvoxpopuli I've done something similar using existing APIs. Would be nice to avoid the hacky "did-insert" stuff...
I'm using a combination of services and contextual components:
@nullvoxpopuli Woops! Supposed to import like this :) import FaIcon from '@fortawesome/ember-fontawesome/components/fa-icon';
I think that fixed my issue? But this "node_modules/.embroider/rewritten-packages" thing seems to fall out of sync sometimes.
@nullvoxpopuli Yeah! Sorry, It's been a while since I've tried this again... I'm getting a Webpack error. I'm just not sure how to import FaIcon properly (`import { FaIcon } from '@fortawesome/ember-fontawesome';`)
@fallsemo hi! I noticed years ago you invited me to collaborate on https://t.co/kzFp4SwaEa. I must've missed that email.
Anyway, i see now that it's archived. I'd be glad to take it on if we can un-archive it. my GH is https://t.co/aHVveRJxYG.