fix: correct `exports` field in package.json

eslint / markdown

Lint JavaScript code blocks in Markdown documents

MIT License

391 stars 60 forks source link

fix: correct `exports` field in package.json #279

Closed ocavue closed 2 weeks ago

ocavue commented 2 weeks ago

Closes https://github.com/eslint/markdown/issues/278

Based on the Node.js docs (link), I can't say for sure that the existing exports field is invalid, but it is certainly uncommon, which might be the issue behind #278. I updated the exports field to a more common format as described in the Node.js docs, and based on my testing, it does fix #278.

linux-foundation-easycla[bot] commented 2 weeks ago

The committers listed above are authorized under a signed CLA.

:white_check_mark: login: ocavue (9edc647c0a2593d9c72056517ed070b2da1b527a, b45bfc61a5cc989e2015fb4eed02eb99a48ede48, 779161613d0b1139be5a285ac5304b5c61073107)

nzakas commented 2 weeks ago

Thanks for the PR! Can you also add an entry for types? It seems like some tools will want that along with the default export.

ocavue commented 2 weeks ago

Added.