devongovett

5 ms·

1.
by devongovett 3y ago
Thanks for the feedback! 1. We decided to start simple for the first release but it’s definitely possible to add something like asChild if the need arises. There are some tradeoffs to this though, eg it’s easier to mess up the DOM structure
2.
by devongovett 3y ago
If you have a trigger inside a nested scrollable region, and the popover pops out of this region, then if the trigger is scrolled out of view the popover cannot be anchored to it anymore.
3.
by devongovett 3y ago
This was an intentional choice. Repositioning when an outer element scrolls is pretty janky in some cases because scroll events don’t fire at 60fps. Also it’s not possible at all in other cases, like if the trigger goes completely out of vi
4.
by devongovett 4y ago
In Parcel 2, you can configure everything.
5.
by devongovett 4y ago
Parcel 2 solved this though. You can override pretty much everything if you want now.
6.
by devongovett 5y ago
We actually already have! I contributed hwb() color support as part of my work on Parcel CSS, and it shipped in Firefox 96! https://github.com/servo/rust-cssparser/commit/62d63fea751df...
7.
by devongovett 5y ago
Yes, there is a WASM build used by the demo: https://parcel-css.vercel.app Not sure if we could reuse these packages though, since we'd need to expose an API from Rust to JS anyway.
8.
by devongovett 5y ago
Hi, author of Parcel CSS here. I have been thinking about implementing the CSS OM spec as the JS API. This is the same API that browsers expose for manipulating stylesheets. The advantage of this is that we don't need to invent somethi
9.
by devongovett 5y ago
I work on React Aria. Adobe is a big company and there are many teams using different technologies. In general, some very new parts of creative cloud chose to use web components, but the majority of teams are using React, and I don't f
10.
by devongovett 5y ago
Haha yes it is. We have to do a ton of manual testing to ensure consistency and compatibility across many devices, browsers, and screen readers. Some of my tweets showing how we do this: - https://twitter.com/devongovett&#x2
11.
by devongovett 5y ago
Yeah ComboBox is one of the most difficult. We wrote a post about the work that went into ours. https://react-spectrum.adobe.com/blog/building-a-combobox.ht...
12.
by devongovett 5y ago
If you want a bundler built using SWC as a base today, check out Parcel: https://parceljs.org
13.
by devongovett 5y ago
And Parcel: https://parceljs.org
14.
by devongovett 5y ago
Next.js still uses webpack. They basically replaced Babel with SWC.
15.
by devongovett 5y ago
I commented elsewhere in this thread but that benchmark is really measuring the performance of Terser, which is used by all of the other tools listed there. Parcel has improved somewhat since that benchmark was last updated but until terser
16.
by devongovett 5y ago
esbuild tends to produce larger bundles due to https://github.com/evanw/esbuild/issues/639 . Looks like there was recent activity though, so we need to re-test. Anyway, there's a plugin available for now:
17.
by devongovett 5y ago
In v2, there is no transpilation unless you add a browserslist config.
18.
by devongovett 5y ago
Note that this benchmark is dominated by Terser for minification. All tools aside from ESBuild use it.
19.
by devongovett 5y ago
This was true in Parcel 1, but v2’s plugin system is just as powerful as webpack’s. v2 is all about adding extensibility and control.
20.
by devongovett 5y ago
Parcel 2 does both: it is useful out of the box, and many projects will never need to configure it, but v2 adds a complete plugin system that lets you override and configure everything too. :)
21.
by devongovett 5y ago
Note that Parcel’s plugin system is completely different in v2 and the implicit loading is gone.
22.
by devongovett 5y ago
We will have a WASM build, yes. Mainly for running in the browser or on platforms we don't build for. In our tests so far, it is significantly slower though (e.g. ~30%) so it's a tradeoff.
23.
by devongovett 5y ago
I started prototyping a @parcel/jest preset and a @parcel/register package that would help with this. Basically it would use Parcel for builds when using other tools like testing frameworks. Potentially we could do something for E
24.
by devongovett 5y ago
I am paid to work on react-aria/spectrum. Parcel is a side project.
25.
by devongovett 5y ago
Yep, this is true. In fact, we already improved performance by over 25x by optimizing algorithms in JavaScript. As covered in the blog post, this rewrite was motivated by more than just performance and does include algorithmic improvements
26.
by devongovett 5y ago
Indeed. There is currently an SWC minifier project that is in progress. The maintainer of Terser is helping with it, and the Parcel team will likely help with that as well after we ship the stable Parcel 2 release. :)
27.
by devongovett 5y ago
Sorry about that. It's difficult to maintain effectively two large open source projects like this simultaneously, especially since this is a side project for most of us. We've probably dropped the ball a little, especially since v
28.
by devongovett 5y ago
Yeah it's pretty bad to have accessibility be a mode though. Also, since it's completely non-standard, the usual screen reader navigation keys don't work as expected and users have to learn a completely custom interface. Bett
29.
by devongovett 5y ago
This is very bad for accessibility. Rendering things in canvas means there is no DOM, which means nothing for screen readers to read. To be fair, the old google docs editor was also very bad for a11y, but at least there was potential to imp
30.
by devongovett 5y ago
Hi, Parcel maintainer here. v2 will be released very shortly. We are ~1 month away from rc. Also, we should have a very big announcement about build perf in the next couple days. Apologies for the long pre-release cycle but I think the ligh

More ›