majo44

Any feedback ?

@cronon The problem with domino + @webcomponents/custom-elements is that polyfill requires global window ( so the document will be also global). For server side rendering, where you will want to...

@cronon I figured out there is possibility to have separate window/document for each request by using eg Zone.js: ``` function runInDomZone(fn) { let window = domino.createWindow(' '); let document: any...

Hi, thanks, good to know that there is declaration: I very like that lib, have simple reasonable api, supports es6, and do not have any dependencies, I checked 20 different...

I noticed this issue when I tried to use paths mapping like: ``` { "compilerOptions": { ... "paths": { "*": [ "*", "./node_modules/@types/*", "./node_modules/*", "./packages/*" ] } } } ```...

Hello, I also looking for such option. For the monorepo, or multiple packages will be very useful to have possibility for share the config, just by referencing the package which...

+1 on our big monorepo (500 packages) we also want to share the `.eslintcache` especially to save CI time.

@robdodson I'm not sure about this point. > If the element is being rendered on the server, and Preact is trying to pass it a object/array, it will not do...

@robdodson For as is transparent where we are rendering the component, on server (domino) or client. Components works exactly in same way on both sides, have same live cycle and...

Hi, we have also this issue. We have huge monorepo (~400 packages/rush/pnpm), we are on the mocha/chai/sinon, and we made a try to migrate package by package to vitests. In...