John

To confirm my understanding; - All module exceptions should be swallowed. - All extension exceptions should be propagated.

Further to this, should the default implementation raise a "Not Implemented" or just do nothing?

Perhaps a 'fail early when debugging'? Things can't always fail gracefully. That's what exceptions were intended for (going back to the original reasons C++ had exceptions added to it). Downside...

> Isn't it the other way around? Extensions only get the sandbox, modules have full access. I'd also deduce that from the names "extension" -> something peripheral, non-critical, and "module"...

Hi, I forked the project and made a stab at the changes [(fork)](https://github.com/morrijr/color-convert/commit/1cf1aa0727c63ae718c1d6cc988c6c57c67321aa) but I've two failing tests... lines 118 and 120 in test/basic.js. assert.deepStrictEqual(convert.ansi16.ansi16(103), 103); assert.deepStrictEqual(convert.ansi256.ansi256(175), 175); But I'm...

PR #66 created (failing tests commented out for now). I'll close this issue and we can continue on the PR?

's been a while, anything I can do to progress this?

Would it be possible to get just the negative spaces, where the cutouts currently are? That would allow people to more easily create their own shells and cut/subtract the key...

Rather than sticking with the git mechanism, would it be possible to use the built-in package manager in a similar manner to how ebastler has? https://github.com/ebastler/marbastlib?tab=readme-ov-file#how-to-install I think they're using...

The point is to get kicad to do the download and setup for you. Not to get each person to manually download and install.