TWIL May 22nd 2026
- Talking to open source maintainers (even within your company) about an idea is good to do before you make a PR
- You might find their reasoning is very different, even if both your approaches achieve the same goal
- It's possible to install React Compiler in your React 19 project and have it do absolutely nothing
- For example, if you used webpack (for some reason) and delegated handling of TS files exlusively to
ts-loader - When the plugin that does the React Compiler stuff is a babel plugin
- And
babel-loaderonly handles JS files
- For example, if you used webpack (for some reason) and delegated handling of TS files exlusively to
- ESM and CJS interop can cause a lot of complicated issues
- If you don't use hashes, maybe a CSP can just be written to
index.htmlat build time?- Should probably use hashes though
- Or at least send the CSP as a header
- If you have a network call in your
useEffect, be really careful with its dependecy array - In the iOS SDK, if you add a new function to the SDK you need to build it for AwesomeApp to know about the new function
- Despite them both being in the same repo
- And the Android SDK not needing to be built in the same situation
Links
- @scope - MDN
Huh, did not know about this one. At first glance you might wonder why not just nest everything under the parent component, but @scope also lets you define a lower bound for the selector. so you can do
@scope (.article-body) to (figure) {
img {
border: 5px solid black;
background-color: goldenrod;
}
}
and select every image in the article body that's not in a figure.
- @import - MDN
Another CSS thing I surprisingly didn't know (or forgot); @import is actually CSS not Tailwind!