Simen Bekkhus
Simen Bekkhus
FWIW, I tried enabling type info in the [Jest monorepo](https://github.com/facebook/jest), quite quickly running into an OOM (without enabling any rules we don't already run) We get an OOM both with...
Woah, almost double issue number 🎉
@arcanis I tried a `yarn workspaces foreach exec yarn npm audit -R` and I get a failure in just `jest-website`, the others exits successfully. So it seems to be some...
Not to be that person, but any updates on this? Lerna doesn't seem like it's actively maintained anymore, so I'd love to remove the dependency and just rely on yarn...
Thanks for the update @arcanis! Writing a custom plugin sounds a bit much for evening hacking, but I'll take a look. Maybe @nicolo-ribaudo wants to share his thoughts in this...
Adding `import` condition above `require` condition should fix it
my suggested solution would be here in `rxjs`
I wonder if node can do something to improve the native realpath. The promise api uses the native implementation under the hood (https://nodejs.org/api/fs.html#fs_fspromises_realpath_path_options), so it'll probably become more prevalent
@duykhang53 that makes sense - it's the same API. My point was that it shouldn't be up to consumers to deal with these issues, it should be fixed upstream in...
For the "I need to load `package.json`" use case, why not do something like this: ```js const {sync: pkgUp} = require('pkg-up'); const packagePath = pkgUp({ cwd: require.resolve('uuid') }); ``` https://github.com/sindresorhus/pkg-up...