Should I worry about this error: "Error: Cannot resolve a relative module identifier with no parent module"


#1

I have an app that works using components within components.
Everything was just fine until a couple of weeks ago when I started getting errors.

“Error: Cannot resolve a relative module identifier with no parent module”

The app still works but should I worry? I cannot define the routes in an absolute manner, it would be too much work and I would loose flexibility.

I’ve included a screenshot of the error.

Thanks


#2

It might mean that one module is loading twice. Latest steal should tell you which one.

This can be fine, just your build is bigger than needed, or it can cause weird errors depending on what the module does.


#3

Thanks @justinbmeyer it might be related to duplicate imports. I’ll try to clean up the code to make sure this is the case.


#4

@justinbmeyer I was finally able to fix this error and it was due to the same module loading twice. I had to move the import to the upper level though and now I don’t get any warnings.

Thanks