Please add package.json to exports

[IanVS]

I would like to check the version of the content-tag that is being imported in my project, but cannot because package.json is not included in the subpath exports specified by the project. Would you be willing to add ./package.json to your exports?

Edit: after looking a little closer, it looks like exports has been specified since very early versions, so adding it now won't really help me, but I think it's still a good thing to do for future users.

[NullVoxPopuli]

are you able to use a tool like: https://github.com/yjl9903/unplugin-info
to get versions in to your project?

[mansona]

I agree that we should add it (i happen to be in the camp of people that think it should be auto added in node but there is some disagreement on that 😞)

If you're doing this sort of check in your build script you can use require.resolve(content-tag) and then use something like pkgUp to walk up to the next package.json. It's not ideal but it works

[IanVS]

@NullVoxPopuli thanks for pointing that out, but that doesn't seem like what I need. I'm consuming content-tag, and need to be certain that I'm getting a compatible version, whereas that tool seems geared towards getting the version of your own application.

I've solved my issue by checking for startByte directly in runtime. If you're really curious why I need to do that, it's because I'm making content-tag an optional peer dependency in a PR that adds support for ember template tags to my import sorting prettier plugin: IanVS/prettier-plugin-sort-imports#231. I saw that you had landed a similar PR in the Trivago project, but that implementation sorts all comments below imports, and it's important to my plugin to maintain comments at the top of files or alongside imports, so I went a different direction.

@mansona yeah I can see arguments on both sides for auto-adding it or not, but I do tend to think it's at least best practice to add it manually so long as you don't have a good reason for preventing it from being accessed. Thanks for considering it!

[NullVoxPopuli]

I'm fine with a package.json entry being added to exports

[NullVoxPopuli]

and it's important to my plugin to maintain comments at the top of files or alongside imports, so I went a different direction.

exciting!!!!

The implementation in the Trivago project is just "simplest".
it's using a very basic import parser, so that that plugin doesn't actually need to parse files