Mike Donnalley

Sounds like a solution has been reached. I'm going to close this issue - please feel free to open a discussion if there' more to discuss

Closing this since I can't reproduce it using the latest `@oclif/core` - please feel free to open a new issue in the oclif/core repository if you're still experiencing this. ```typescript...

This should be resolved on the latest versions of oclif/core and core - if not, feel free to open a new issue

@shrutiburman Is this still an issue for you? If so, could you provide a repository that replicates the issue? Thanks!

@shazron After more deliberation, we decided that this isn't something we're able to fix because it would eliminate support for separating values by spaces, which is widely used by our...

Deno support is not currently on our roadmap because there's simply not enough demand for it and we (that is, Salesforce) don't have any plans on using deno for our...

@WikiRik Sorry, I forgot to update the labels on this. We're planning on addressing this in the [next major](https://github.com/oclif/core/discussions/1040)

You can you use [dotenv](https://www.npmjs.com/package/dotenv) in CLI's bin/run.js to load a .env file

`bin/run.cmd` just runs `bin/run.js` so whatever you do in there should also work for windows

@JensAstrup I'm not able to reproduce this with the following: - `oclif generate gh-1060 --yes` - copy example into `src/commands/hello/index.ts` - `bin/dev.js --name oclif` Is there anything I'm missing? Also...