Izhaki

Add at the top: ``` const path = require('path') ``` It's a core module.

That's because babel does not build anything outside the current `cwd`. You'd need to override the ignore option to only include node_modules. This is how I do this, albeit with...

Can this issue be closed?

Fresh `npm install` doesn't work: "babel-plugin-module-resolver": "3.1.0", "eslint-import-resolver-babel-module": "4.0.0", "babel-core": "^6.26.0", "eslint": "^4.15.0", Per @psychobolt suggestion, this solves it: "babel-plugin-module-resolver": "^2.7.1", "eslint-import-resolver-babel-module": "2.2.1",

Sure. Will try to slot this in tomorrow.

This could help? https://medium.com/trabe/getting-rid-of-finddomnode-method-in-your-react-application-a0d7093b2660

[This one big condition](https://github.com/vvo/iron-session/blob/dab76011ee9951b358db5e7d80dad45cb5453043/src/index.ts#L99-L109) can be broken down into multiple conditions, each providing more specific error: ```ts if ( !req || !res || !userSessionOptions || !userSessionOptions.cookieName || !userSessionOptions.password ) {...

You can do just that if you want. Nothing stops you from adopting the same approach (just use `useUser` instead of `useSession` and follow the next-auth example). But having looked...

Same issue here. Related: https://github.com/karma-runner/karma/issues/1868

Oddly, we are using RTK, but soon we'll have to port some of our system into a system using Rematch, and the question surfaced again... why Rematch? I think it...