Joakim Hedlund

@ljharb I tried writing a regression test that I expected to fail when I commented out my change in the rule but I cant seem to figure out how the...

I've gathered that `testFilePath` is just a helper to resolve the path to the fixtures directory. The test itself is a copy of one of the existing cases in `tests/src/rules/no-unused-modules.js`...

> update the web panel to support this new provider Oh, I didn't see any references to specific providers in the web/ directory so I assumed it would work out...

Same here, `[email protected]` uses 1.3.8 from Github, but then fails because the tarball doesn't have the files in the root directory: ``` npm ERR! Could not install from "node_modules/jspdf/file-saver@github:eligrey/FileSaver.js#1.3.8" as...

@makc Fair question :) Like you discovered, the actual commit/tag is fine and that's why I suspect that it's trying to download the zip or tarball from the release page....

Like @_makc_ above, installing it explicitly seems to do the trick, for somereason 😕 ``` npm i 'file-saver@github:eligrey/FileSaver.js#1.3.8' ```

After tinkering a bit with it and trying to wrap my head around how hooks actually work, I think I understand it now (but would love to get confirmation): Essentially,...

I'm having the same issue. My host machine runs Docker version is 26.1.0 [which _does_ support basepath](https://github.com/moby/moby/issues/47687), but `louislam/dockge` is still on 24.0.7 which I presume is the version that...

Hi aanu1994, Normally I only create tags for the supported Lambda runtimes which are linked to LTS releases. I see that Node 22 was released recently (2024-04-24), would that work...

`22.x` is now published. Thanks for the assist, @yq314 :)