nfroidure/common-services

A module to gather some very common services

Projects

Stats

common-services's Issues

Move mocks outside of the module

Mocks are messing up the module code would be better to have another module or nothing at all instead.

Make the `resolve` service use `import.meta.resolve`

To fully rely on the ESM module system, we still need to use import.meta.resolve to load files dynamically:
https://github.com/nfroidure/common-services/blob/main/src/services/resolve.ts#L43-L50

We will probably need to rely on the main file of the program so a MAIN_META_URL could be used to resolve any module from the projet root location. This will be usable with the --experimental-import-meta-resolve flag and the parent option of import.meta.resolve but in the meanwhile, we will probably need to cut the URLs by hand.

We could also add a counter that add some query string to be able to load the files in the same process after some changes: https://nodejs.org/api/esm.html#urls . It would be useful to avoid caching.

Convert to TypeScript

node_modules are included in the published package

There is a node_modules folder in the downloaded package from npm.
There are only @types and type-fest that are included but those 2 make the package quite heavy (+ 3.7M)

Better testing for `resolve` service

Currently, Jest doesn't support the import.meta.resolve function so we can't test it.

Depends on jestjs/jest#14923

Error using package with Typescript

I get the following error when using the package with Typescript

node_modules/common-services/dist/process.d.ts(1,23): error TS1452: 'resolution-mode' assertions are only supported when `moduleResolution` is `node16` or `nodenext`.