Module not found: Error: Can't resolve './styles/evaluators', and many more about model-viewer HOT 5 CLOSED

There's no way anyone can help without some background on what you're trying to do. It appears you're trying to build MV into your own TS project of some kind? Are you using a particular framework for that? There must be something wrong with how the dependency or import is specified, so maybe start by showing those from your code?

from model-viewer.

i am using React for this. as usual i have imported the MV in the App.js file import @google/model-viewer and using it across the app

from model-viewer.

"as usual" makes it sound like you've done this before and it's worked with model-viewer? Did something change recently? We don't have any React experience on this team, but others on our forums do and we know they've used it successfully, so it's probably some kind of import magic. Have you searched our discussions yet?

from model-viewer.

I assume @Pratik610 is using Webpack because if so version 5 of Webpack has a breaking change that requires imports to have a file extension. The relevant section is below. There is a flag to use the legacy behavior. I will try the flag as I am having the same issue. Ideally the file extensions could be added to model-viewer as well.

Imports in ESM are resolved more strictly. Relative requests must include a filename and file extension (e.g. *.js or *.mjs) unless you have the behaviour disabled with fullySpecified=false.

from model-viewer.

@chamby Thanks! PRs welcome if you find a change that will simplify this for users.

from model-viewer.