unexpectedjs/unexpected

The extensible BDD assertion toolkit + webpack support hotline :)

Gustav Nikolaj

@gustavnikolaj

Using autoprefixer will solve that for you, and I actually do use just that, so I'll yield that point to you ;)

Sune Simonsen

@sunesimonsen

Safari users don't deserve gaps :joy:

Peter Müller

@Munter

tight...

Gustav Nikolaj

@gustavnikolaj

But I think the overall principle still stand. I'm willing to accept a non-zero amount of production facing issues like that, if it means that my tool chain will be that much simpler

Sune Simonsen

@sunesimonsen

The version I have installed supports gaps :sweat_smile:

Peter Müller

@Munter

I think at this point that's fair. And I was actually being a bit of a devils advocate there, because what we do right now is exactly what you describe. However I run a fast moving single product in a growth phase. I don't maintain 30+ webapps that need a consistent behavior

Sune Simonsen

@sunesimonsen

Nicely played :D

Gustav Nikolaj

@gustavnikolaj

!! :)

I have the other situtation you describe, with many different, but slightly similar, applications. I haven't found a way that I'm comfortable with, to manage them all without tooling overhead. So my coping mechanism is to keep things simple

If a setup breaks in some app I can blast away the bundler, test runner etc, and have things up and running again within 15 minutes. That's only possible because we shy away from as much custom stuff as possible

About the only custom thing we do is to import stylesheets from js

but most bundlers support that

Sune Simonsen

@sunesimonsen

If a setup breaks in some app I can blast away the bundler, test runner etc, and have things up and running again within 15 minutes. That's only possible because we shy away from as much custom stuff as possible

Exactly

Gustav Nikolaj

@gustavnikolaj

I actually considered adding a rule to my eslint setup, requiring that you put the .js-extension imports to close the gap towards browser-based esm

I think people will get annoyed with me, but it seems like a good idea to me. We will have to start doing that eventually, and it will make it easier to get things working without a build-step

Andreas Lind

@papandreou

With a bit of luck they'll just yell at eslint :)

Peter Müller

@Munter

It's not too hard to create a fix rule, so you can have eslint autofix it for you ;)

Andreas Lind

@papandreou

Yeah, it's a good way to turn your opinions into law :)

Gustav Nikolaj

@gustavnikolaj

For all the talk about keeping things default and avoiding custom stuff like the plague.....

Do you guys have any experience with alternatives to require.context in webpack? I'd like a way to glob all files matching a specific pattern, and then use import to code-split each of them into their own bundle. If I use require.context I'll just end up with all in the same bundle

Andreas Lind

@papandreou

You mean like https://webpack.js.org/api/module-methods/#dynamic-expressions-in-import ?

Or without webpack?

Gustav Nikolaj

@gustavnikolaj

Yeah, but I need to be able to have a glob pattern across subfolders. Webpack only is fine

Andreas Lind

@papandreou

I remember having fought that at some point, and also helped implement the equivalent thing in the assetgraph system.js integration, so I can at least say that it's hairy! But I don't know off the top of my mind.

Gustav Nikolaj

@gustavnikolaj

Yeah, you need to plugin in a pretty early phase. I don't think it's possible without a custom plugin at this point. At least not if you want to be able to have bundle barriers at those points

Gustav Nikolaj

@gustavnikolaj

The easy, non webpack specific fix, is to just have a pre-start script that will build a js file with a bunch of paths in an array that I can import :)

Andreas Lind

@papandreou

If there's no bundle splitting etc. required, yeah

Gustav Nikolaj

@gustavnikolaj

Right, I'd need to actually generate the code from the list of values.


export default {
  "./path/to/file.js": () => import('./path/to/file.js'),
  // ...
}

Andreas Lind

@papandreou

Gustav Nikolaj

@gustavnikolaj

The main drawback is that you'd have to restart webpack for it to pick up on new matches

Andreas Lind

@papandreou

That's a nice low-tech way to do it if that stuff doesn't change all the time

I wonder if you also need to "memoize" the imports to avoid re-importing, or if the browser has a module cache.

Gustav Nikolaj

@gustavnikolaj

what would the browsers module cache do here? isn't it translated to webpacks bundle format?

or are you talking in the non-webpack case?

Andreas Lind

@papandreou

Ah, right, webpack's loader will handle it

But yeah, also the non-webpack case. I'm revealing my agenda of having the dev setup work without a bundler ;)

Gustav Nikolaj

@gustavnikolaj

I'm almost a little ashamed to admit, but what I'm doing is a reimplementation of react storybook. :p I got sick and tired with upgrading the real one. It's such a simple tool but they manage to make it progressively worse and worse.

Andreas Lind

@papandreou

Sounds like you should just have stayed on the old version :)

Gustav Nikolaj

@gustavnikolaj

Yeah, but that meant that I would be prevented from upgrading webpack

Andreas Lind

@papandreou

Argh....

Gustav Nikolaj

@gustavnikolaj

Yeah, just my thought

Andreas Lind

@papandreou

This discussion is making me depressed.

Gustav Nikolaj

@gustavnikolaj

hehe

my new version is very simplistic - it's actually quite close in terms of being able to work without webpack

I don't think you should get depressed as much as just reinforced in your goals about having a working dev setup without a bundler.

All of these problems come from people building "neat tools that work great", and people trying to "make it easy for junior developers".

Gustav Nikolaj

@gustavnikolaj

I'll stop before I loose the grip :D

Andreas Lind

@papandreou

Yeah, I know you're one of the good guys :heart:

Sune Simonsen

@sunesimonsen

You see my motivation for making a new platform even if it is a totally stupid mission 😝

Sune Simonsen

@sunesimonsen

I'm lazy loading here but Rollup figures out how to hash the sub bundles and everything if I include this plugin.

Where communities thrive

People

Repo info

Activity