Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
dmchaplin opened this issue Nov 20, 2024 · 3 comments
Open
Labels

Comments

@dmchaplin
Copy link

dmchaplin commented Nov 20, 2024

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();
@abdulsattar
Copy link
Collaborator

abdulsattar commented Nov 20, 2024

@dmchaplin Thanks for the PR! However, according to glob documentation:

absolute Set to true to always receive absolute paths for matched files. Set to false to always receive relative paths for matched files.
By default, when this option is not set, absolute paths are returned for patterns that are absolute, and otherwise paths are returned that are relative to the cwd setting.

Since our pattern is absolute, it should always be absolute. And, on my machine (mac), I see that it's absolute. Is that not the case on your machine? Is it dir.fullPath that's not absolute or is it glob that's not returning absolute paths?

@dmchaplin
Copy link
Author

@abdulsattar Thanks for the response.

I did a quick check. dir.fullPath is returning the full directory so it appears to be the Glob. It's strange that Glob is not returning the Default behavior. I use a PC but I don't know if if I have global setting somewhere that is overwriting behavior.

I appreciate the work you did to get multiple directories supported! This tool has so much protentional and a huge step forward from the old Local Dev Server.

Copy link

git2gus bot commented Nov 22, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants