Upgrade: v7 convert to ESM lets Disscuse the API about del

[sindresorhus]

I plan to move directly to ESM without any CommonJS support. I'm just waiting for TypeScript 4.7 (which will have full ESM support), so I don't have to deal with too many TS support issues.

The API will be two named exports: delete and deleteSync.

It's probably easier if I do the migration myself as there's a lot of details to get right.

https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c

[sindresorhus]

Does that mean you'd like to convert this library to TypeScript and compile both CommonJS and ESM?

No. The TS mention is about TS not being able to handle ESM until TS 4.7.

[frank-dspeed]

Review: #140 it demonstrates why i want the api change as there is no other good upgrade path at last i do not see it.

[frank-dspeed]

@sindresorhus i am specialist for the new ESM support in typescript 4.7 and got bad new for you and some good as long as you output a single entrypoint your package.json needs the following to be compatible to typescript moduleResolution node12 + nodenext

{
  "main": "name.js",
  "types": "name.js",
  "type": "module",
  "exports": "name.js"
}

note that you can use the .cjs and .mjs extensions with this example typescript 4.7 will then lookup: name.d.mts or name.d.cts
there is no fallback to index.d.ts!

{
  "type": "module",
  "exports": { 
    "node": { 
      "import": "./name.js",
      "types": "./name.js"
    },
    "import": "./name.js",
    "types": "./name.js"
  } 
}

the above example uses the object form and also droped types and main fild as they are not needed this will only work with moduleResolution: node12 nodenext so it is not backward compatible add main and types to stay typescript backward compatible also it shows that you need to add types for each nested level.

when you use a Object for exports a lot of edge conditions can apply this was the most basic version for a esm only module

also be aware that subPath Patterns are not supported by typescript as soon as you use them your on your own

when you want the object form you need to add a types fild to each alias and to the root alias this is WiP but the root level works and there is no option to choose the conditions that typescript will use

• microsoft/TypeScript#46452
• microsoft/TypeScript#47931

[jonkoops]

I plan to move directly to ESM without any CommonJS support. I'm just waiting for TypeScript 4.7 (which will have full ESM support), so I don't have to deal with too many TS support issues.

Does that mean you'd like to convert this library to TypeScript and compile both CommonJS and ESM?

[jonkoops]

I have an implementation ready for this issue under #143.