Felix

Cheerio 1.0 is out, only a short seven years after the first release candidate. Read more here: cheerio.js.org/blog/cheerio-1… Thanks to everyone that helped along the way!

@mark__lawlor We are building a design system in Tailwind and are looking to get a native build of the library by swapping out primitives and using NativeWind. Tailwind can produce a CSS file to go with our JS. Is there an equivalent for NativeWind? (Or would the CSS file suffice?)

@fb55 If you don't care able those features, I personally think that NativeWind just adds overhead, and your better just using react-native-css-interop directly. Its not documented yet, but it powers NativeWind and is designed to be used by component libraries

Coming soon, NativeWind v4 brings a significant enhancement to the native styling experience. With CSS variables, media and container queries your applications can now be more dynamic and responsive. Demo: @mwlawlor/hello-world-v4" target="_blank" rel="nofollow noopener">snack.expo.dev/@mwlawlor/hell… Explore the new features and capabilities👇

@mark__lawlor What are your thoughts on building libraries using NativeWind 4? Will it be possible to precompile styles (as NativeWind 2 enabled), or will there always be a need for NativeWind to be included in the consuming app?

And a whole bunch more. Over the next couple of days I'm going to be talking about these features in more depth and talking about what they fix and now allow. Reply here if you've got any questions

In our first five minute maintainer video, we get to chat with @fb55! Watch to learn more about Felix’s journey in open source: bit.ly/3J5ra5k

@MattMueller @golivebud Congrats on the launch!

Brought @golivebud to life today, brushing off some very rusty design skills 😅 Cute enough? Anything I should add?

I am in love with the app icon of @AnOtterRSS

parse5@7.0.0 is out, which has been a big focus of mine since taking over as a maintainer five months ago. All the deets at github.com/inikulin/parse…

TIL that source maps can point to URLs for source files, using the `sourceRoot` property. This allows you to publish NPM packages with source maps, *without* including the original source. For TypeScript, this does the trick:

We’ve had an Amazon Fresh store for a few months now right next to our home. My favorite part of the cashier-less experience is that I don’t feel awkward bringing in groceries from a different store. Amazing for combining trips.

@adamdbradley Very cool! There is going to be some low-hanging fruit left in terms of tree shaking for now, but that can be addressed later. I am also starting to think about a future road map – let me know if there is anything you’d like to see!

@fb55 Awesome, looking forward to it. I'm building a minimal dom implementation that runs well in edge servers and the esm exports will be a big improvement.

@fb55 awesome work on porting parse5 to typescript! Is 6.0.1 not what's in main right now? I'm looking forward to using the esm version. thanks!

I am curious how Telegram emoji codes for calls are generated. This one from last night perfectly summarized the call, before it even happened. And that wasn’t the first time.

@1Password I have considered writing my own app to deal with bank cards on the web. 1Password is already a big step up over iCloud Keychain, as that doesn’t support storing verification numbers. But it still feels like an afterthought of a feature.

Bank card handling in @1Password really has so much low-hanging fruit. (1) Please flag that cards are about to expire. (2) Why aren’t card networks inferred from the number? (3) Why aren’t card numbers validated? (4) And why can’t I just scan my card with my camera?

Seeing this Gmail auto-complete: My heart goes out to all of the knowledge workers stuck in the same meeting for weeks.

@patrick_lorio AssemblyScript (assemblyscript.org), which is ~a subset of TypeScript. Great target when your starting point is in TypeScript 😃

@fb55 Which language are you using to target web assembly? I only went so far as doing a hello world example with rust a few months ago and it seemed to be quite nice.

I tried to introduce WebAssembly into one of my NodeJS modules today. Tl;dr it isn't ready for prime time yet.

I am genuinely hyped about what's to come with WebAssembly and AssemblyScript. For now, the complexity of calling the module, and the need to use Node >= 14.8, ultimately made me put a pin in this.

I was able to call the WASM-ified module and extract enough information that I do think things work. And yes, the speed-up is dramatic (~80% faster or so, although result extraction is going to reduce that number).