Borewit

> "docx" is used for macro-free (non-template) documents, while "docm" is used for macro-enabled (non-template) documents.

Sounds good to me, why don't you create a PR? Can you link to some supporting documentation or reference material?

Small reminder @hackermd

@sindresorhus, following [your guidance](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c#how-can-i-make-my-typescript-project-output-esm) I changed `["module": "node16", "moduleResolution": "node16"](https://www.typescriptlang.org/tsconfig#module)` and declared ``compatibility with Node.js engine ≥ version 14.16. Yet I see integration tests are passing with latest Node.js 12....

@sindresorhus, can you merge this one. I formally released those dependencies as normal versions on your request.

I never managed to get the unit test running stable via karma-browserstack. After being idle a while (not sure how long, maybe an hour) there is reasonable probability it works....

Same issue. In my case it was caused the normalization of the absolute [`full`](https://github.com/TypeStrong/dts-bundle/blob/2ca1591e890dc4276efc4bb0893367e6ff32a039/lib/index.ts#L715) path of the same module ended up as: 1. `C:\Users\Borewit\code\github\music-metadata-browser\node_modules\music-metadata\lib\index.d.ts` 2. `C:\Users\Borewit\code\github\music-metadata-browser\node_modules\music-metadata\lib`

It looks like one of my imports `./` instead of `./index` maybe the source of the problem.

@steniowagner can you please review?

I don't what is going on with the CI tests, units tests pass on my end. I double check the metadata is extracted.