Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge bin/mocha and bin/_mocha #2292

Closed
segrey opened this issue Jun 1, 2016 · 5 comments
Closed

Merge bin/mocha and bin/_mocha #2292

segrey opened this issue Jun 1, 2016 · 5 comments
Labels
semver-major implementation requires increase of "major" version number; "breaking changes" stale this has been inactive for a while...

Comments

@segrey
Copy link
Contributor

segrey commented Jun 1, 2016

Tools providing integration with mocha need to use bin/_mocha sometimes. For example, debugging mocha test is possible with bin/_mocha only, because it's impossible to pass --debug-brk=<port> option to _mocha child process from bin/mocha.
Well, it's easy for IDE to use bin/_mocha under the hood, but it might be not so obvious for users who debug mocha tests using node-inspector. Though, there is a hint, one need to take it into account. Also, debugging npm script that runs mocha tests leads to the same confusion (e.g. this WebStorm issue).

Related to #1969 (comment) //cc @boneskull
Please merge bin/_mocha and bin/mocha to have single public main script file in mocha3. Thanks.

@boneskull
Copy link
Contributor

Yes, having one (1) executable is definitely on the todo list.

@boneskull boneskull added semver-major implementation requires increase of "major" version number; "breaking changes" and removed major-release labels May 24, 2017
@ScottFreeCode
Copy link
Contributor

See also #2517, the --node-arg flag in npx (which is bundled with newer versions of npm), and the ability to just say node <arguments> node_modules/mocha/bin/mocha.

@github-actions
Copy link
Contributor

This issue hasn't had any recent activity, and I'm labeling it stale. Remove the label or comment or this issue will be closed in 14 days. Thanks for contributing to Mocha!

@github-actions github-actions bot added the stale this has been inactive for a while... label Mar 28, 2021
@segrey
Copy link
Contributor Author

segrey commented Apr 10, 2021

Would be great to have a single executable.

@github-actions github-actions bot removed the stale this has been inactive for a while... label Apr 12, 2021
@github-actions
Copy link
Contributor

This issue hasn't had any recent activity, and I'm labeling it stale. Remove the label or comment or this issue will be closed in 14 days. Thanks for contributing to Mocha!

@github-actions github-actions bot added the stale this has been inactive for a while... label Aug 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver-major implementation requires increase of "major" version number; "breaking changes" stale this has been inactive for a while...
Projects
None yet
Development

No branches or pull requests

3 participants