forcedotcom / lwc-dev-server-feedback

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

lwc-dev-server has incorrect peer dependency "@lwc/engine@1.0.x" #49

Closed iandrosov closed 4 years ago

iandrosov commented 4 years ago

I am getting this error while update SFDX lwc-dev-server warning "@salesforce/lwc-dev-server > @webruntime/compiler > @lwc/rollup-plugin@1.0.2-222.18" has incorrect peer dependency "@lwc/engine@1.0.x"

My node version: v10.16.0 SFDX CLI version: sfdx-cli/7.36.0-b1c4e9c7c8 darwin-x64 node-v10.15.3

KrisGraySFDC commented 4 years ago

Thank you! I think its just a warning, and we're working to address it in an update next week.

KrisGraySFDC commented 4 years ago

We delayed the part of the update which would have addressed the warning. Thanks for reporting it, we're still trying to squash it.

AltiusRupert commented 4 years ago

Hi @KrisGraySFDC, better hurry up : LWC local dev was announced at the Release Readiness webinar last week ;) Good luck

KrisGraySFDC commented 4 years ago

Updates are happening to enable it, it's going to be beautiful.

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-7299192

amansaw commented 4 years ago

@KrisGraySFDC - Got the same issue after I updated lwc server plugin today in vscode. Is there any fix for this one ?

amansaw commented 4 years ago

@KrisGraySFDC - Whenever the server starts and I want to go to my components, this is the page that I see with no link whatsoever. A simple page without any navigation to lwc components. image

Doondireddy commented 4 years ago

@KrisGraySFDC I too have the same blank page as @amansaw ,

When I Inspect the page, this is the output.

lwc_Error

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-7677120

lcampos commented 4 years ago

This was fixed in release 2.1.0 and above. Thanks for reporting this.