extra dependencies needed? #18
-
This is great, but to get it working, I also needed to install some extra dependencies:
at least when using There is also this part at the top of the docs:
Should they all be listed in the install command? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @nktnet1, thanks for checking out the tool. The docs (here) assume you have these base packages already configured as part of your LWR/SFDX project. It might not be such a bad idea to have a sub-command ready with these extra packages for those that don't already have them installed. I'd have bundled them with the core package, but didn't want to lock end users into specific package versions which may conflict with other tools.
These two packages ARE baked into the LWC Garden package by choice, so don't require to be installed by consumers of LWC Garden. LWC Garden uses the more advanced module resolving provided by said packages to resolve its own source LWCs. The docs are there to mention their usage and allow you to potentially take advantage of the extra features they provide in your own configurations (e.g. namespacing folders, multi-folder namespacing - similar to on-platform folder structures). |
Beta Was this translation helpful? Give feedback.
Hi @nktnet1, thanks for checking out the tool.
The docs (here) assume you have these base packages already configured as part of your LWR/SFDX project. It might not be such a bad idea to have a sub-command ready with these extra packages for those that don't already have them installed.
I'd have bundled them with the core package, but didn't want to lock end users into specific package versions which may conflict with other tools.
These two packages ARE baked into the LWC Garden package by choice, so don't require to be installed by consumers of LWC Garden. LWC Garden uses the …