[Bug]: Failed to resolve entry for package "@materializecss/materialize about materialize

[danice]

Hello,
Materialize-docs is an example of using materialize from a vite project. Can you provide an example project to test this issue?

Thanks!

[axelf]

@danice i made i git repository: https://github.com/axelf/materialize-vite
You can downlaod the code and after a npm install and npm run dev you see the error:

[axelf]

This is working: import { M } from "@materializecss/materialize/dist/js/materialize.js";
This is the path of the main entry of the package json.
But why isimport { M } from "@materializecss/materialize"; not working?

It is working, but this says the editor if i hover over the import statement:

Could not find a declaration file for module '@materializecss/materialize/dist/js/materialize.js'. '/myproject/node_modules/@materializecss/materialize/dist/js/materialize.js' implicitly has an 'any' type. If the '@materializecss/materialize' package actually exposes this module, try adding a new declaration (.d.ts) file containing declare module '@materializecss/materialize/dist/js/materialize.js';ts(7016) module "/myproject/node_modules/@materializecss/materialize/dist/js/materialize"

[danice]

it's because the package has also this entry that takes preference in the import:
"module": "src/index.ts",

This "module" was not causing problems when importing the library using webpack and it make it work when using it as a workspace (as in materialize-docs).

I think we should replace "src/index.ts" here by the ".d.ts" that your comment says. But we should check that it keeps the library working when used from webpack and as a workspace.

[axelf]

@danice thank you for helping me out.

For now should i leave the import as it is import { M } from "@materializecss/materialize/dist/js/materialize.js and ignore the error in my code editor? I don't mind the marking in the editor and it works like this for now