Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Found no LWC components in the current workspace. (Relative / Full Path)

Offen
#261 4 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
typescript
Bereich
cli

Rechercherichtung

Start in index.ts at the namespacePaths glob construction and compare the paths passed to the LWC server with the package directories. Reproduce with the listed sf lightning dev command on Windows Git Bash, then verify the workspace reports the expected 55 LWC components instead of none.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

BUG P3
Summary

Local dev is not finding LWC directories. While starting the plugin, I get the follow error:

[Module Graph] Found no LWC components in the current workspace, check your settings in lwc.config.json.
[LWC Dev Server] LWC Dev Server started at port:8081
Steps To Reproduce:
  1. Using Git Bash
  2. SF_LOG_LEVEL=trace SF lightning dev app -t desktop -n "My Cool App"
Expected Result
[Module Graph] Found 55 LWC components in the current workspace.
Actual Result
[Module Graph] Found no LWC components in the current workspace, check your settings in lwc.config.json.
Additional Information

Logs:

From the CLI log:

{"level":10,"time":1732135128486,"name":"sf:LightningDevApp","msg":"Starting LWC Dev Server with config: {\"rootDir\":\"C:\\\\Users\\\\CAALJ60\\\\VSCode\\\\employee-performance-management\",\"port\":8081,\"paths\":[\"sfdx-source\\\\epm\\\\main\\\\ui\\\\lwc\",\"sfdx-source\\\\localDev\\\\main\\\\ui\\\\lwc\"],\"workspace\":\"SalesforceCLI\",\"identityToken\":\"aACp9dNvSrqd48D+vJeT8ZDxCGIeDEi9Nr4FhbYLR68=\",\"logLevel\":5,\"lifecycle\":{\"listeners\":{\"telemetry\":[null],\"warning\":[null],\"command_incomplete\":[null],\"plugins:preinstall\":[null],\"update\":[null],\"prerun\":[null],\"preparse\":[null],\"sf-doctor-@salesforce/plugin-auth\":[null],\"sf-doctor-@salesforce/plugin-deploy-retrieve\":[null],\"init\":[null],\"sf-doctor-@salesforce/plugin-trust\":[null],\"plugins:preinstall:verify:signature\":[null],\"jit_plugin_not_installed\":[null]},\"uniqueListeners\":{},\"logger\":{\"pinoLogger\":{}}},\"clientType\":\"desktop\"}"}
System Information

Git Bash

 »   Warning: @salesforce/plugin-lightning-dev is a linked ESM module and cannot be auto-transpiled. Existing compiled source will be used instead.
{
  "architecture": "win32-x64",
  "cliVersion": "@salesforce/cli/2.66.7",
  "nodeVersion": "node-v20.18.0",
  "osVersion": "Windows_NT 10.0.19045",
  "rootPath": "C:\\Users\\CAALJ60\\AppData\\Local\\Programs\\node-v20.18.0-win-x64\\node_modules\\@salesforce\\cli",
  "shell": "C:\\Users\\CAALJ60\\AppData\\Local\\Programs\\Git\\usr\\bin\\bash.exe",
  "pluginVersions": [
    "@dx-cli-toolbox/sf-toolbox-aep-utils 0.7.5 (user) published 265 days ago (Thu Feb 29 2024)",
    "@dx-cli-toolbox/sfdx-toolbox-package-utils 1.0.1 (user) published 14 days ago (Wed Nov 06 2024)",
    "@dx-cli-toolbox/sfdx-toolbox-utils 0.1.2 (user) published 947 days ago (Mon Apr 18 2022)",
    "@oclif/plugin-autocomplete 3.2.8 (core)",
    "@oclif/plugin-commands 4.1.7 (core)",
    "@oclif/plugin-help 6.2.16 (core)",
    "@oclif/plugin-not-found 3.2.25 (core)",
    "@oclif/plugin-plugins 5.4.15 (core)",
    "@oclif/plugin-search 1.2.14 (core)",
    "@oclif/plugin-update 4.6.10 (core)",
    "@oclif/plugin-version 2.2.15 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.21 (core)",
    "@oclif/plugin-which 3.2.17 (core)",
    "@salesforce/cli 2.66.7 (core)",
    "apex 3.5.6 (core)",
    "api 1.3.1 (core)",
    "auth 3.6.72 (core)",
    "community 3.3.2 (user) published 18 days ago (Sat Nov 02 2024) (latest is 3.3.4)",
    "data 3.11.2 (core)",
    "deploy-retrieve 3.15.8 (core)",
    "info 3.4.17 (core)",
    "lightning-dev 1.9.3 (link) C:\\Users\\CAALJ60\\VSCode\\plugin-lightning-dev",
    "limits 3.3.38 (core)",
    "marketplace 1.3.4 (core)",
    "org 5.1.2 (core)",
    "packaging 2.9.0 (core)",
    "schema 3.3.40 (core)",
    "settings 2.4.4 (core)",
    "sobject 1.4.44 (core)",
    "telemetry 3.6.19 (core)",
    "templates 56.3.28 (core)",
    "trust 3.7.39 (core)",
    "user 3.6.2 (core)",
    "sfdmu 4.36.7 (user) published 22 days ago (Tue Oct 29 2024)",
    "sfdx-git-delta 5.49.4 (user) published 6 days ago (Thu Nov 14 2024)"
  ]
}

OS:
Windows 10 Enterprise

Initial Theory

Relative Paths are being passed to the server config, but it expects full paths.
Prior to 1.9.1 full paths were used.

This change in index.ts works makes it work fine.

  const namespacePaths = (await Promise.all(packageDirs.map((dir) => glob(`${dir.fullPath}/**/lwc`, { absolute : true })))).flat();
Vorherrschende Sprache
TypeScript
Sterne
19
Forks
19
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus salesforcecli/plugin-lightning-dev

Alle Issues in salesforcecli/plugin-lightning-dev

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.