Closed james-nair closed 1 year ago
Apparently this can't be fixed with patch-package too as it doesn't comparing package.json. Anyone has any work-around? (Also thank you @amcdnl for looking into this)
@JimmyNair - The types
export is there - https://github.com/reaviz/reaflow/blob/master/package.json#L27
@JimmyNair - The
types
export is there - https://github.com/reaviz/reaflow/blob/master/package.json#L27
Hi @amcdnl , I did see the 'types' exports in the source code. However it is not reflected in the output package.json, which is being downloaded. Please see attached screenshot from npm. As you can see it's not part of the exports.
Interesting - OK let me investigate
This has resolved in version 5.2.2. Thanks @amcdnl
I'm submitting a...
Current behavior
Importing components from "reaflow" in react project, with typescript 5.1.3 in vscode workspace, and "moduleResolution" set to "bundler" in tsconfig.json, vscode would throw a
Could not find a declaration file for module 'reaflow'
.Inspecting the package.json of "reaflow" in the node_modules, in fact missing the "types" field under "export". See below:
Expected behavior
Importing components from "reaflow" should not throw any errors in vscode.
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
This bug prevent the project being able to build (at least without
"noImplicitAny"; false
in tsconfig.json)Environment