search

forcedotcom / lwc-dev-server-feedback

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

Support for multi-package project structure #121

Open nathanlb opened 2 years ago

nathanlb commented 2 years ago

Is your feature request related to a problem? Please describe. We're developing a library of LWC components we release as an unlocked package. The components are not usable on their own so we'd like to also provide a package of recipe components showcasing how to best use them. We'd also like to run e2e cypress tests on a set of components built out of our library components. This set of test components we wouldn't package with the library either.

Currently we cannot use the awesome lwc-dev-server as much as we would like because it doesn't support dependencies between packages of a same project.

Describe the solution you'd like

  1. The aspiration: The ability to point the dev server to a package containing lwc components composed of lwc components from another package from the same project. (ie. inter-package dependency)
  2. The dream: (part 1) + The ability to preview all lwc within a project with multi-package structure. Moving between them using the package selection side menu for example.

Describe alternatives you've considered

Additional context Big fans of the dev server and all its potential.

AllanOricil commented 2 years ago

Related https://github.com/forcedotcom/lwc-dev-server-feedback/issues/88

AllanOricil commented 2 years ago

The dev server should create symlinks between all folders/dependencies a dev is currently working on, and not just one single folder within a sfdx project.