search

forcedotcom / lwc-dev-server-feedback

LWC Local Development
BSD 3-Clause "New" or "Revised" License
45 stars 10 forks source link

Better error messages #87

Closed AllanOricil closed 4 years ago

AllanOricil commented 4 years ago

Is your feature request related to a problem? Please describe. Yes, eslint is not indicating what is the problem with my component, and neither the console or the dev server messages are saying anything. There is no way for me to find where it is wrong.

image

image

Describe the solution you'd like Enable source maps by default.

stale[bot] commented 4 years ago

This issue has been automatically marked as type:bug-p3 because it has not had recent activity.

git2gus[bot] commented 4 years ago

This issue has been linked to a new work item: W-8448194

lcampos commented 4 years ago

Thanks for opening this issue @AllanOricil. We made some changes that provide accurate error information when previewing a component in version 2.6.0. I'll close this issue since it's been fixed.

AllanOricil commented 4 years ago

@lcampos I'm still seeing non helpful error messages

image

This test component is just wrapping another component that I need to the test. It is very simple image

All the packages are updated to the latest version image

AllanOricil commented 4 years ago

I understood the problem. It was a typo in the component's name that I was referencing from inside the test component. You could add a message saying "We can't find the component Foo that is referenced inside the component Bar."