Christopher Hiller

so you’re suggesting rather that Mocha provides a way to run tests with `mocha` but behind a flag that won’t pollute `global`?

part of what makes mocha mocha and part of its success is that it doesn’t require boilerplate to import stuff. despite the dogma around polluting the global namespace there are...

@leotm here's an example of including windows in a build matrix: ```yml jobs: build: name: Node.js v${{ matrix.node_version }} / ${{ matrix.os }} runs-on: ubuntu-latest strategy: matrix: node_version: [18, 20]...

Has npm decided if this is a bug, yet? `package-lock.json` churns wildly, and this is part of the problem. Even if this is intended behavior, it's not _nice_.

@wraithgar https://github.com/boneskull/pkg-lock-churn

As shown in the example repo and from my experience, it only seems to affect dev deps unless someone has a counterexample. I don't know if automated conflict resolution causes...

To cause the conflict? Switch to the `conflict` branch then `git rebase main`

1. In `package.json`, the resolution should take both changes; i.e. add `prettier` _and_ `eslint` 2. In `package-lock.json`, no manual resolution; run `npm install` after step 1.

@wraithgar Can you reproduce?

**Workaround** > TL;DR: Remove all `node_modules` dirs before resolving via `npm install` To prevent this from happening repeatedly, I've adopted the following strategy for resolving `package-lock.json` conflicts: ```bash rm -rf...