Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,9 @@
".": {
"types": "./dist/index.d.mts",
"default": "./dist/index.mjs"
}
},
"./dist/*.wasm": "./dist/*.wasm",
"./package.json": "./package.json"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand .wasm, but what is package.json needed for?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

happy to drop it - I have no particular need of it, but added it as I often do in case people need to check the version of the package that is installed, e.g.:

import pkg from 'harfbuzzjs/package.json'

echo(pkg.version)

the alternative, should this be needed, is doing strange things to find the directory of the package, and then readFileSync - but of course this is theoretical as I guess no one's asked for this yet!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Drop it then, please.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@khaledhosny, the package.json export was dropped but the PR’s title wasn’t revised, which made the automatically generated change log inaccurate: https://github.com/harfbuzz/harfbuzzjs/releases/tag/v1.6.1

Comment thread
danielroe marked this conversation as resolved.
Outdated
},
"files": [
"dist"
Expand Down
Loading