Busticated

> Any plans to have a build for the M1? yes, in time. we're basically downstream of Node.js (which [added support](https://github.com/nodejs/node/issues/37309) as of `v16`), `node-usb` (which seems to have [added...

i moved this back into "draft" state to calm the reminders. i don't see us merging this anytime soon if only b/c it's so out of date but it's a...

thanks @xHergz 🙏 if you haven't already, please review and sign our [Contributor License Agreement](https://docs.google.com/a/particle.io/forms/d/1_2P-vRKGUFg5bmpcKLHO_qNZWGi5HKYnfrrkd-sbZoA/viewform)

any chance of this landing? i just got bit by this due to having to work-around the issue - see here: https://github.com/actions/setup-node/issues/376#issuecomment-989378800

hi @gregvanl thanks for taking a look 👍 if you are referring to: > Note: When a command is invoked from a (context) menu, VS Code tries to infer the...

@michelengelen thanks for taking a look 🙏 i'll try what you suggest and report back. one thing right off the top though, from the docs you linked: >By default, the...

🤔 i'm a bit stumped on what exactly is meant by "intrinsic dimensions". i added the `autoHeight` prop to the `` component itself and wrapped it with a `` component...

ah, thanks 🙏 i took a quick run at updating the template but ultimately hit weirdness when trying to update `vitest` to `v0.34.x`. testing lib queries seem broken: ``` TestingLibraryElementError:...

deprecated as of `[email protected]` - see #133 and [breaking changes](https://github.com/vitest-dev/vitest/releases/tag/v0.34.0)

it would be super-helpful to have docs around testing components which invoke `useFetcher()` specifically. short of mocking it out entirely, i haven't had much luck sorting it out on my...