Pelle Wessman

If its open for anyone to join then I can try to join if it works for me CET-time

An update for those following this issue but haven't kept up to date with meeting minutes and Slack discussions: I believe the ambition now is for this to be discussed...

Maybe we need to add some performance regression tests as these kind of things are hard to reproduce without a representatively large type graph. The reasoning for the change in...

> I think we should create a survey for collaborators to see what are the pain points of being a Node.js collaborator and how to improve the environment. To build...

> Node.js core collaborators maintain the [nodejs/node](https://github.com/nodejs/node) GitHub repository. The GitHub team for Node.js core collaborators is @nodejs/collaborators. Collaborators have: > > * Commit access to the [nodejs/node](https://github.com/nodejs/node) repository >...

> retaining collaborators is as important as making new one Exactly, that's why I was interested in the reasoning to limit this deep dive to existing collaborators :) > We...

@skagedal Regarding `mocha`, we're crunching our way through it, there are quite a few old dependencies in that package. Feel free to open an issue there if there is none...

> during the production deployment when using in Nuxt 3 application Why is ESLint getting installed in your production deployment? 🤔

@Aravinda93 My understanding is that this issue is only applicable to the dev dependencies of eslint itself, so it should not impact your project You can use a `npm why...

New PR to fix this: https://github.com/actions/setup-node/pull/702