question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

re-clone mocha-webpack repo?

See original GitHub issue

there is a lot of useful blame history that could be used from the mocha-webpack repo - is there a reason you dropped all the git history?

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:9 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
larixercommented, Mar 1, 2019

Thanks @alecf and @akosipax. The history from mocha-webpack repository has been transferred into this repo.

0reactions
paxcodescommented, Feb 28, 2019

Hey @vlasenko, I believe this set of git commands will work (thanks to @alecf for the repo and I didn’t have to figure out how to apply the changes).

git clone https://github.com/alecf/mochapack.git

# remove origin which is currently alecf's repo
# optional, but if you’re not going to remove this, you have to do some renaming
git remote rm origin 

# This is my repo in this command. You'd have to replace it with your repo. 
# You'd have to recreate (delete, then create) this repo so you can still use 
# "mochapack" as the project name
git remote add origin https://github.com/akosipax/mochapack.git

See the result in my own account: https://github.com/akosipax/mochapack

It has the commit history + no note about it on top being a fork. I do believe that git history is valuable. Having the git history will point us right away to the appropriate issues, and PRs.

Or maybe faster for you would be for me to transfer my repo’s ownership to yours. Either way, you’d have to delete this repo to prevent name clashing. What do you think?

Read more comments on GitHub >

github_iconTop Results From Across the Web

mocha-webpack/webpack-configuration.md at master - GitHub
Another important thing is to stop webpack from bundling your libraries inside your node_modules folder. This can be easily done by using the...
Read more >
mocha-webpack - npm Package Health Analysis - Snyk
Ensure you're using the healthiest npm packages. Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice.
Read more >
Introduction · mocha-webpack - GitHub Pages
mocha -webpack is basically a wrapper around the following command... $ webpack test.js output.js && mocha output.js ... but in a much more...
Read more >
Mocha Test Exception occurred while loading your tests
We have mocha-webpack to compile and run the test files. ... I even cloned this repo into another folder but I still have...
Read more >
Run your Tests using Node.js and Mocha frameworks
json 0.0s => [test 1/2] RUN npm ci 6.5s => [test 2/2] COPY . . Now that our test image is built, we...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found