update package.json with files array

[hilleer]

Use files property in package.json to explicit show what files are included (in contradiction to .npmignore where you specifically exclude "some" files).

This way one avoids accidentally publishing non-compiled code like src/ folder etc:

Note that a bunch of files are always considered when publishing and does not have to be listed in the list accordingly to the docs:

[swarthy]

Hi! The src folder is included in the package intentionally, because it is convenient for debugging errors occurring inside the library. Why it is necessary to remove it?

[hilleer]

Hi! The src folder is included in the package intentionally, because it is convenient for debugging errors occurring inside the library. Why it is necessary to remove it?

You can close it if that is the intention 👍 I thought it was a mistake and potential gain for reducing the size of the published library slightly. Is there any use of the source code for users of the library?

[CatchMe2]

Hi, I'm facing some TypeScript issues due to the included src folder. I have an ESM package with verbatimModuleSyntax option enabled in tsconfig.json. Type-check is reporting:

node_modules/redis-semaphore/src/errors/LostLockError.ts:1:1 - error TS1287: A top-level 'export' modifier cannot be used on value declarations in a CommonJS module when 'verbatimModuleSyntax' is enabled.

1 export default class LostLockError extends Error {}
  ~~~~~~

Removing src folder from node_modules resolves the issue. How about excluding src from the package?

[kibertoad]

@swarthy If you intend to keep shipping ts files, can they at least be made compatible with verbatimModuleSyntax option?

[swarthy]

Released in v5.6.2

[kibertoad]

@swarthy Thank you, the change helped!