The package.json of codemirror-graphql points to files that do not exist
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 1.9k
- Avg merge
- 22h 45m
- Merged PRs (30d)
- 70
Description
I think there is some kind of mis-configuration in the building or publishing process related to the `codemirror-graphql` package. The sub-modules usually have the `ESM` folder exported but this one... well it doesn't.
The `main` and `module` properties are pointing to files/folders that do not exist.

**Some examples:**
1. `codemirror-graphql` (**bug**, no ESM folder exported)
https://unpkg.com/browse/codemirror-graphql@1.0.2/
2. `graphql-language-service-interface` (yes, ESM folder exported)
https://unpkg.com/browse/graphql-language-service-interface@2.8.4/
3. `graphql-language-service-parser` (yes, ESM folder exported)
https://unpkg.com/browse/graphql-language-service-parser@1.9.2/
4. `graphql-language-service-server` (yes, ESM folder exported)
https://unpkg.com/browse/graphql-language-service-server@2.6.3/
**Considerations:**
1) It seems that the `ESM` files are scattered within the root folder rather than in the `/esm` sub-folder on the registry version
2) I forked the `codemirror-graphql` package and I built it according to configuration and the **`esm` folder is correctly created** ... _but this doesn't reflect the published version_ on the `npm` registry.
3) This seems a long time bug affecting all previous releases
NPM Registry: https://unpkg.com/browse/codemirror-graphql@1.0.2/
My build:

Contributor guide
Assessment
This issue has not been assessed yet.