Filip Dupanović

@saadq this is a nice suggestion! It's a quick and easy way to author library definitions when needed. Unfortunately, when done as such this creates local dependencies which we can't...

It should be possible for someone to publish an NPM package with library definitions that declare types for many related dependencies, unless I'm mistaken. Something that would provide something similar...

@jedwards1211 there's a more detailed discussion about publishing happening here https://github.com/flow-typed/flow-typed/issues/3083.

@staabm I think GH will always ZIP uploaded artifacts, so it's not possible to use their storage service for viewing HTML. From [About Workflow Artifacts](https://docs.github.com/en/free-pro-team@latest/actions/guides/storing-workflow-data-as-artifacts#about-workflow-artifacts): > Artifacts are uploaded during...

> You probably use more of the library than you realise. I remain a bit unconvinced by this statement. Even after dispatching a report, the perf tools are saying that...

@mattdyoung fair point that my cursory tests can't be considered realistic. I actually haven't looked at the monorepo much while doing all the major upgrades and seems that [providing a...

~I've been using the same workaround from @yyvess successfully, but on the latest release started getting the error again.~ :point_up: just realized that `request` and `page.request` use a separate context...

What is the exact problem, though? It seems that `html-webpack-plugin` expects the template loader to return a template function, i.e.: ``` const template = require('./index.nunjucks') template(context); ``` Instead of: ```...