Gluegun not able to parse windows filesystem to execute commands
See original GitHub issueI have a directory structure like this commands/mycommand/subcommand.js
So ideally when using the gluegun framework, clibrand mycommand subcommand
my subcommand.js should get invoked. it works fine on my Mac and Unix machine but doesn’t get invoked in my windows machine. Is it a filesystem issue which gluegun is not able to comprehend?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:24 (11 by maintainers)
Top Results From Across the Web
Jamon on Twitter: "@JS_Jedi @innthomas @blackbeardcoder ...
We're going to build a command-line app that will let us analyze a code ... STEP 2 Let's use `npx` to run Gluegun's...
Read more >gluegun: Versions | Openbase
system: run command -- adds stdout to error object when it throws an error (#727 ... most dependencies (fs-jetpack and enquirer were not...
Read more >Cannot install with npm package from git - Stack Overflow
npm ERR! fatal: Could not read from remote repository. For whatever reason when asking for public (!) repo it needs key.
Read more >How to fix a Read-Only drive in Windows | Scottie's Tech.Info
Maybe you just had to run a disk check that asked you to reboot. ... it just means that Windows can only read...
Read more >gluegun | Yarn - Package Manager
filesystem - moving files and directories around ⚒ system - executing other command-line scripts http - interacting with API servers
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
@jamonholmgren Just validated the CLI with the latest version of Gluegun and the above-mentioned issue seems to have been mitigated 👯♂️
I’ve also given @cmckni3 the ability to cut NPM releases so we can tighten up our release cycle.