Bug: Types are not found wth nodenext module resolution

[bramvbilsen]

The types for croner are not being found in my Typescript application. I installed the package as follows:

npm i croner

The specific errors:

'.../node_modules/croner/dist/croner.min.cjs' implicitly has an 'any' type.

I made sure to include all node_modules paths for types in my tsconfig.json file:

// tsconfig.json
{
    ...
    "moduleResolution": "nodenext",
    "typeRoots": [
        "./src/types/*",
        "./node_modules/*",
        "./node_modules/croner/types/*" // Added this for completeness sake
    ],
    ...
}

The issue appears to be with moduleResolution being nodenext. The import does not show any errors if I switch it to use node. But, unfortunately, this breaks compatibility for other packages and is not an option.

Any ideas?

[Hexagon]

Hmm, interesting! Will have a look at that later, which version of typescript do you use?

[bramvbilsen]

Hmm, interesting! Will have a look at that later, which version of typescript do you use?

Wow, thanks for the quick reply!
Using Typescript version ^4.8.4

[Hexagon]

Found some pointers here, microsoft/TypeScript#50466

Will fix this asap 👍

[Hexagon]

@bramvbilsen Trying to set up a test environment to reproduce this behavior. Do you have "type": "module" or not in your package.json? How does your import statement look like?

[bramvbilsen]

@Hexagon No the package.json is just the default "type": "commonjs"

[Hexagon]

Oh, i see. Seems like croner need to export separate type definitions for commonjs (.d.cts)... Interesting stuff indeed!

[Hexagon]

@bramvbilsen Proposed fix released in 6.0.0-dev.1. Had to bump major version as it changes file structure of distributed files.

Please test by

npm install croner@dev

[Hexagon]

Released in 6.0.0. Please reopen if you still have problems with this.

[bramvbilsen]

My apologies for the late reply. Version 6.0.0 works perfectly, thank you!