Short answer: you can't.
import statement in another js module inside a directory with jsconfig.json in the root directory.
In addition to this, the jsconfig.json file is never deployed to the org, meaning it cannot be referenced from a LWC.
Possible Solution: Use a script to generate and store a static list of LWCs
Assuming you have all your LWCs locally:
- Create a static resource
lwc_list.resource-meta.xml (see below for contents)
- Run the script below, relevant to your OS to generate a list of LWCs
- In your LWC import the resource
import lwcList from '@salesforce/resourceUrl/lwc_list'
- Split the contents by the new line character (\n) and iterate through it in your markup
ls -d */ > ../staticresources/lwc_list.txt
dir /a:d /b > ../staticresources/lwc_list.txt
<?xml version="1.0" encoding="UTF-8"?>
<description>Generated list of Lightning Web Components</description>
Future Solution: Query for Lightning Component Bundles using Apex
There was a request via Twitter to expose LightningComponentBundle much like how you can query AuraDefinitionBundle currently. https://twitter.com/tahir_farhan/status/1085939366764134401?s=09
With this object exposed, you could call an Apex method that queries LWCs in your org and display a list in the component. However, there hasn't been an update for months.