David Burles

Web application architect, educator, tinkerer, and developer. Hosts @graphqlmelb

[David Burles @dburles]

@tmeasday @storybookjs Just signed up to early access this morning :)

[David Burles @dburles]

Just published scoped-style-components for React. Scope styles natively. CSS-in-JS without the runtime!
https://t.co/CxfICuIjin

[David Burles @dburles]

Here's a basic working prototype: https://t.co/rfAC0DeB1l

[David Burles @dburles]

Looks like native CSS-in-JS is totally possible with CSS scoping! Here's a basic implementation I've been playing around with:

[David Burles @dburles]

There's already wide browser support with just Firefox being an exception. However support should be landing soon: https://t.co/IreFu8tVwD

[David Burles @dburles]

@StatisticsFTW @AwokeKnowing @dhh I suppose in a way it sort of fills the role of what bundling achieves and negates the need to actually bundle

[David Burles @dburles]

@StatisticsFTW @AwokeKnowing @dhh No

[David Burles @dburles]

Are you using GraphQL with REST API's? Optimal REST API design for GraphQL with DataLoader
https://t.co/CLwm9mFPQf

[David Burles @dburles]

@dan_abramov @mjackson To be clear, this makes bundlers completely redundant.

[David Burles @dburles]

@dan_abramov @mjackson Possibly! take a look at this https://t.co/egtejpMQDW. It's server middleware that resolves a module graph at request time and generates modulepreload link relations.

[David Burles @dburles]

@cramforce @jacobrask @jacobsenscott @dbackeus A build isn’t required, just server middleware. Though you could also include it as part of a static HTML build to negate that requirement.

[David Burles @dburles]

@cramforce @jacobrask @jacobsenscott @dbackeus Definitely, but I believe both those issues can be solved without requiring bundling. Nested dependencies do cause request waterfalls, however I have found a potential solution to that without bundling, but I haven’t tested it in the wild yet.

[David Burles @dburles]

@cramforce @jacobrask @jacobsenscott @dbackeus There are constraints but there are so many benefits and comparatively little downsides that there’s no question that it’s the right solution. For an excellent explanation see: https://t.co/EuOUOTH66g

[David Burles @dburles]

@jacobrask @cramforce @jacobsenscott @dbackeus This is the real problem. Packages shouldn’t be published assuming they’re going to be tree shaken and bundled. The irony is they can be published in a way to support no bundling and bundlers will also work perfectly fine, actually they’ll have far less work to do.

[David Burles @dburles]

@cramforce @dbackeus There are ways to avoid request waterfalls without bundling

[David Burles @dburles]

@cramforce As I mentioned in the original thread. This might be a solution to the problem of module request waterfalls:
https://t.co/MEBND93IRd

[David Burles @dburles]

@dhh Related: I've just released a tool that will prevent request waterfalls for JavaScript modules https://t.co/egtejpMQDW. It generates modulepreload link relations based on a files module graph. Deeply imported modules will now load in parallel.

[David Burles @dburles]

@tehmhithorphe @dhh @remix_run Remix does use modulepreload, but for preloading chunks of the built application. This provides references to the graph unique to each module.

[David Burles @dburles]

@AwokeKnowing @dhh Just feed it the path to a module and it will resolve the module graph as an array. This can then be transformed into modulepreload link relationships for the HTTP Link header. Or for `link` elements, which could potentially be done as part of a build process for a static app.

[David Burles @dburles]

Prevent module request waterfalls with one simple middleware https://t.co/egtejpMQDW