fix: npmignore

[lishaduck]

Fixes #1432.

I think it'd make more sense to use files instead here, but 🤷‍♂️

[lishaduck]

Updated attw output:

eslint-plugin-jsdoc v1.0.0

Build tools:
- [email protected]

👺 Import resolved to an ESM type declaration file, but a CommonJS JavaScript file. https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/FalseESM.md

💀 Import failed to resolve to type declarations or JavaScript files. https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/NoResolution.md

⚠️ A require call resolved to an ESM JavaScript file, which is an error in Node and some bundlers. CommonJS consumers will need to use
 a dynamic import. https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/CJSResolvesToESM.md

🥴  Import found in a type declaration file failed to resolve. Either this indicates that runtime resolution errors will occur, or (mor
e likely) the types misrepresent the contents of the JavaScript files. Use -f json to see the imports that failed to resolve. https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/InternalResolutionError.md

🤨 CommonJS module simulates a default export with exports.default and exports.__esModule, but does not also set module.exports for compatibility with Node. Node, and some bundlers under certain conditions, do not respect the __esModule marker, so accessing the intended default export will require a .default property access on the default import. https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/CJSOnlyExportsDefault.md


"eslint-plugin-jsdoc"

node10: 🟢
node16 (from CJS): 👺 Masquerading as ESM
node16 (from ESM): 🟢 (ESM)
bundler: 🟢

***********************************

"eslint-plugin-jsdoc/getJsdocProcessorPlugin.js"

node10: 💀 Resolution failed
node16 (from CJS): ⚠️ ESM (dynamic import only)
node16 (from ESM): 👺 Masquerading as ESM
bundler: 🟢

***********************************

"eslint-plugin-jsdoc/iterateJsdoc.js"

node10: 💀 Resolution failed
node16 (from CJS): ⚠️ ESM (dynamic import only)
🥴 Internal resolution error
node16 (from ESM): 🥴 Internal resolution error
👺 Masquerading as ESM
bundler: 🤨 CJS default export
🥴 Internal resolution error

***********************************

I'd be happy to move it to tsdown or zshy, but I'm not going to refactor all of the package's tooling without prior agreement.

[brettz9]

As I recall, where files is present, referencing a GitHub fork as a package.json dependency had problems as the desired files weren't present. In any case, I'd like to keep it as is for now.

Re: tsdown or zshy, how bad are the diffs expected to be?

[github-actions]

🎉 This PR is included in version 52.0.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[lishaduck]

As I recall, where files is present, referencing a GitHub fork as a package.json dependency had problems as the desired files weren't present. In any case, I'd like to keep it as is for now.

Makes sense 👍
(although, that is what pkg.pr.new is for...)

Re: tsdown or zshy, how bad are the diffs expected to be?

Not awful?
Shouldn't require too many (any?) changes to src/, just the dist/ & associated configs.

[brettz9]

Re: tsdown or zshy, how bad are the diffs expected to be?

Not awful? Shouldn't require too many (any?) changes to src/, just the dist/ & associated configs.

If it can improve our TS output without switching to TS source (like #1223), that'd be great.