Expose more internal resolve logic
See original GitHub issueA lot of the functions in both lib/async.js
and lib/sync.js
would be useful to reuse. I want to write a quick resolve-glob
module (using this and glob), but right now that’ll result in me copying/duplicating 90% of the logic that already exists here. Would you be open to a PR to correct this?
Issue Analytics
- State:
- Created 9 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Expose resolver logic to plugin context #641 - evanw/esbuild
I have a need to be able to call esbuild's internal resolution logic. So it would be better - and faster - to...
Read more >Extend Logic with Your Own Code - OutSystems documentation
Integration Studio allows you to develop extensions in advanced integration scenarios between existing enterprise systems and OutSystems.
Read more >Sharing build logic between subprojects Sample
This sample shows how build logic in a multi-project build can be organized ... Java libraries that use the third subproject as an...
Read more >Secure traffic between Standard logic apps and Azure virtual ...
Secure traffic between Standard logic app workflows and virtual networks in Azure using private endpoints.
Read more >Managing Your Internal Dialogue | SkillsYouNeed
Learn more about how to hear and control your internal dialogue, or your thoughts, to encourage yourself to think more positively.
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
It was so long time ago! Guess all is fine now
I’m going to close this, but am happy to reopen if use cases are provided.