Feature request: Support for wildcards "@module-name/*": "./modules/*"
See original GitHub issueFeature request
Instead of writing
"_moduleAliases": {
"@module-name/moduleA": "./modules/moduleA",
"@module-name/moduleB": "./modules/moduleB",
"@module-name/moduleC": "./modules/moduleC",
}
it would be handy to just write:
"_moduleAliases": {
"@module-name/*": "./modules/*"
}
@ilearnio Or is it possible to achieve this with a custom handler function?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:8
Top Results From Across the Web
Module declaration wildcards #5101 - facebook/flow - GitHub
While stubbing out most modules is easy to do by just doing: declare module 'module-name' { declare module.exports: any; } Some modules ......
Read more >latest - Environment Modules
pattern may contain wildcard characters. Multiple versions of an application can be supported by creating a subdirectory for the application containing ...
Read more >Example of Modules, Tasks and Elements
Listed below is an example of a Project with two modules. In the first module, named "Main", it performs four different tasks. The...
Read more >GN Reference - Google Git
This page is automatically generated from gn help --markdown all . ... the module name of target under compilation (see "module_name" variable).
Read more >Feature Request: Allow wildcards in Windows Event Log input
Currently I know of no way (that I can find) to specify in the input to collect all event logs using wildcards in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@davestewart Thanks for the tip! I’ve already got it working by using tsconfig-paths
Instead of running
I just run
It will automatically pick up the paths from tsconfig.json
@ilearnio @Kehrlann Should this issue be closed now?
Oooh. This is a more complicated project, with
ts-node
… Can’t get it to work here, runningnpx ts-node services/users
and such. I might take a look tomorrow but can’t promise anything.Simple project: https://github.com/kehrlann/module-alias-library`. It shows multiple things, but I just added an alias “wildcard” showing exactly what you mention. Run it with
node index.js