[BUG]: Cannot import used-pm from within ESM

[sounisi5011]

Description of the bug

used-pm/README.md

Lines 27 to 33 in f724043

	In `esm` / `typescript`:
	```ts
	import currentPackageManager from 'used-pm';
	const { name, version } = currentPackageManager();
	```

When this code is executed, Node.js throws the following error:

(node:14784) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)
.../node_modules/used-pm/dist/esm/index.js:1
export default () => {
^^^^^^

SyntaxError: Unexpected token 'export'

Steps To Reproduce

0. Go into the new directory and create a package.json file with the following contents:

   {
     "scripts": {
       "foo": "node bar.mjs"
     }
   }

1. Run npm install [email protected]

2. Create a bar.mjs file with the following contents:

   import currentPackageManager from 'used-pm';
   console.log(currentPackageManager());

3. Run npm run foo - This command should fail with the following error:

   $ npm run foo
   
   > foo
   > node bar.mjs
   
   (node:14989) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
   (Use `node --trace-warnings ...` to show where the warning was created)
   .../node_modules/used-pm/dist/esm/index.js:1
   export default () => {
   ^^^^^^
   
   SyntaxError: Unexpected token 'export'
   ...

Additional Information

In order for a file with a .js extension to be interpreted as an ESM, you need to add "type": "module" to the package.json file.
Node.js and TypeScript will detect the "type": "module" in the package.json file in the nearest parent directory.
see package.json and file extensions - Modules: Packages | Node.js v20.1.0 Documentation

In the case of used-pm, I would suggest creating a dist/esm/package.json file after the build with the following content:

{"type":"module"}

[sounisi5011]

This bug has been fixed in [email protected]. Thank you so much!