Anders Grendstadbakk

It will also solve #109

Yes I'm not the one to say if this is a feature that belongs here or not. But of all the libraries I found this was the one I thought...

I think I figured something out. I followed https://www.drupal.org/docs/upgrading-drupal/upgrading-from-drupal-8-to-drupal-9-or-higher, but had to add `drupal/core`: ``` composer require drupal/core-recommended:^9.0.0 drupal/core-composer-scaffold:^9.0.0 drupal/core:^9.0.0 --update-with-dependencies --no-update composer require drupal/core-dev:^9.0.0 --dev --update-with-dependencies --no-update composer update...

Removing `drupal/core` seems to work.

What seems to work is: ``` composer require drupal/core-recommended:^9.0.0 drupal/core-composer-scaffold:^9.0.0 drupal/core:^9.0.0 --update-with-dependencies --no-update composer require drupal/core-dev:^9.0.0 --dev --update-with-dependencies --no-update composer update composer remove drupal/core ``` Only tested locally, but that...

I suddenly started seeing this error too today. It does not happen on the initial build of `eleventy --serve` but if I save a markdown file afterwards it fails. It...

I had the same problem, but solved it by increasing the timeout of proxy_read and proxy_send in NGINX: https://stackoverflow.com/a/71384705/437385

You could probably change this: ``` function seenreq(options){ var Repo = require("./repo/repo_"+((options && options.repo)||"default")+".js"); this.repo = new Repo(options); var Normalizer = require("./normalizer/normalizer_"+((options&&options.normalizer)||"default")+".js"); this.normalizer = new Normalizer(options); } ``` to something...

Or maybe it requires some try-catch, I'm not that familiar with Webpack.

I will try to make a reduced example 👍