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

Mochapack a fork of mocha-webpack released with Mocha 6 support #308

Open
larixer opened this issue Feb 26, 2019 · 14 comments
Open

Mochapack a fork of mocha-webpack released with Mocha 6 support #308

larixer opened this issue Feb 26, 2019 · 14 comments

Comments

@larixer
Copy link

larixer commented Feb 26, 2019

Hi there, mocha-webpack users!

mocha-webpack has no activity since May, 2018. We at SysGears are maintaining a fork here:
https://github.com/sysgears/mochapack

A new version of mochapack@1.1.0 has been released today with Mocha 6 support.

Check it out!

@shockey
Copy link

shockey commented May 21, 2019

I've made a fork as well! @kyleshockey/mocha-webpack.

If you're still on webpack@2/webpack@3, you might find it useful. AFAICT, mochapack@1.0.0 was made on top of mocha-webpack@2.0.0-beta.0's code, so if you're not already on webpack@4 there's no way to move to it from mocha-webpack.

Edit: I've since moved on to Jest, so my fork is no longer maintained.

@FullStackAlex
Copy link

Mochapack isn't maintained neither...
sysgears/mochapack#19

@FullStackAlex
Copy link

@Vlasenko why did you block me? :)
Maybe you should instead put your energy in maintaining the fork as promised?

@larixer
Copy link
Author

larixer commented Jul 31, 2019

@tech-nomad You have been blocked because you have started to spread fear, uncertainty and doubt in comments here and in mochapack project. The mochpack is maintained, the new releases are being made, new features are being added and security fixes are being incorporated. If you think you can maintain mocha-webpack better - you are free to make the fork and do so the way you can and want.

You fail to understand what open source software is, nobody owes you here. How much money have you paid, how many pull requests have you opened, what else constructive have you done? Nothing? The only thing you have done to the project - is spreading toxic comments. And because of that you are not in a position to demand anything.

@FullStackAlex
Copy link

FullStackAlex commented Jul 31, 2019

@Vlasenko
No, you have blocked me because you are irresponsible and have a huge ego and obviously no understanding of open source yourself.

you have started to spread fear, uncertainty and doubt in comments here and in mochapack project.

That sounds like that was my whole intention, which is malicious or just dumb. There is no doubt about the leck of "maintenance" when you don't response to issues for one month or not at all. You did not contribute any help even it is your (ethical) responsibility at least to try it when you make advertise for a fork of a more or less important package in the JavaScript ecosystem. So there is no doubt about leck of maintenance of the package. Which means you've blocked me for spreading the truth instead of somehow to response to the actual issue and proof this way your reliability.

If you think you can maintain mocha-webpack better - you are free to make the fork and do so the way you can and want.

No I can't. But it doesn't mean I can't state an obvious fact and warn people going to rely on your unmaintained package. I am also free to do this. And you are too. So far I did this only twice. So it means something and you should think carefully about your attitude.

You fail to understand what open source software is, nobody owes you here. How much money have you paid, how many pull requests have you opened, what else constructive have you done? Nothing?

No, you seem not to understand quite a lot of things. Yes, you owe me something when I rely in my projects on your work. At least showing some respect by responding to my issues with your package.

I am very glad you mention the money. I think that's where the trouble comes from. Your agency is exploiting Ukrainian labor and has its base in Russian oligarchs tax haven (Cyprus). It tells a lot why you so aggressive and ignorant about issues of the package. Are you expecting the users of your fork to pay you to maintain the package in an adequate way or what? I'm afraid that's what you would love to: instead of doing the promised work - charging 100 bugs per hour for "custom support" with the package.

I pay monthly for software probably more than you pay your average developer in Ukraine! I would rather pay 50 bugs for something useful than to spend one week figuring out how to get things done with all the f**cking pseudo "open source" out there. And that's exactly what I do.

what` else constructive have you done?

Look in to my Github repos, go to toster.ru or to stackoverflow.com and search for Tech Nomad.
Does everybody have to proof their "open source" reputation to get some sh*t done in your repo? You seem not to understand that people are investing their time when relying on any software - it's not only about money. You own me time of my life when I rely on your advertised work and it doesn't work. I've spend almost one week to get Mocha work in my project because of a bunch of irresponsible "maintainers" in the JavaScript ecosystem. So my (and a lot of other peoples) grade of frustration is quite high. All this factors seem not to bother you. You obviously think, only when money flows you have to show some respect.

The only thing you have done to the project - is spreading toxic comments. And because of that you are not in a position to demand anything.

No, again, you've blocked me because you have a huge ego and yourself have a toxic understanding of "open source". I didn't demand on anything - I've just stated facts. And you blocked me, according to the GitHub notification, because of my last comment, which is absolutely harmless (same as the two previous are) and which I wrote only because you answered to my first comment in such an ignorant and arrogant way. So you blocked me only because of your huge, huge ego.

And what actually did you except updating the supported dependency versions and some links?!

Also, everybody who is using this package is in a position to demand on the maintenance of it, especially when you fork an unmaintained package and promise to maintain it.

I don't think this rude reaction to my statement was the best advertise for your company.

@FullStackAlex
Copy link

Lol, one person has already withdrawn a thumb up for your announcement of the fork :D So I'm obviously not alone with my opinion.

@FullStackAlex
Copy link

FullStackAlex commented Jul 31, 2019

By the way:
there is actually no need for any forks so far (at least in my case there wasn't). I've got it work with Webpack 4, Mocha 6 and Toposort 2. I've just added all the latest versions in the package.json and deleted package-lock.json and node_modules and run again:
npm install

Since then I've got Mocha finally work!! No need for forks!

Here are my devDependencies in the package.json:

"devDependencies": {
    "@babel/core": "^7.5.5",
    "@babel/plugin-syntax-dynamic-import": "^7.2.0",
    "@babel/plugin-transform-runtime": "^7.5.5",
    "@babel/preset-env": "^7.3.4",
    "@babel/runtime": "^7.5.5",
    "@vue/cli-plugin-unit-mocha": "^3.9.0",
    "@vue/test-utils": "1.0.0-beta.29",
    "babel-loader": "^8.0.6",
    "babel-plugin-transform-es2015-arrow-functions": "^6.22.0",
    "babel-preset-env": "^1.7.0",
    "browserslist": "^4.4.2",
    "chai": "^4.2.0",
    "clean-webpack-plugin": "^2.0.0",
    "copy-webpack-plugin": "^5.0.0",
    "css-loader": "^2.1.1",
    "express-static": "^1.2.6",
    "file-loader": "^3.0.1",
    "html-webpack-plugin": "^3.2.0",
    "jsdom": "^15.1.1",
    "jsdom-global": "^3.0.2",
    "less": "^3.9.0",
    "less-loader": "^4.1.0",
    "mocha": "^6.2.0",
    "mocha-webpack": "^2.0.0-beta.0",
    "nyc": "^14.1.1",
    "preload-webpack-plugin": "^3.0.0-beta.3",
    "puppeteer": "^1.19.0",
    "sinon": "^7.3.2",
    "style-loader": "^0.23.1",
    "url-loader": "^1.1.2",
    "vue": "^2.6.8",
    "vue-loader": "^15.7.0",
    "vue-router": "^3.0.2",
    "vue-style-loader": "^4.1.2",
    "vue-template-compiler": "^2.6.10",
    "vuex": "^3.1.0",
    "webpack": "^4.29.6",
    "webpack-cli": "^3.2.3",
    "webpack-dev-server": "^3.2.1",
    "webpack-merge": "^4.2.1",
    "webpack-node-externals": "^1.7.2"
  },

@FullStackAlex
Copy link

And why is mochapack actually not a direct fork of mocha-webpack?!

@larixer
Copy link
Author

larixer commented Aug 15, 2019

This project is not the only place where @tech-nomad shows hatred and aggression, without providing any help to the open source community, treating people, like everyone owes him, proof:
shopware/development#21
Behaviour like this is generally unwelcome in any open source project.

The people are investing their time and energy for free. We spend countless hours to develop and support the code and support users who behave constructively, without expecting anything in return. But we are not going to tolerate abusive behaviour. So you deserved your ban and you will be banned everywhere in open source community, until you educate yourself how to behave properly.

@FullStackAlex
Copy link

Good investigative work! Did you observe my flat in Berlin, too?

Yes, as already mentioned in this thread, there is another and so far the only project/repo beside your repo where I criticised the owners.

But there is a small difference: whereas you've blocked me immediately just for stating me the fact of a lack of support and maintenance for the repo (and doing so you was actually the one who is aggressive and full of hate), the Shopware guy I was arguing with in the linked thread called me personally on the phone same day and deescalated the situation by finally listening carefully to my complains. So there is actually no conflict anymore (also because I've stopped using their system which I've spend months to learn but which is in the end not satisfying). Also despite quite hot arguing he didn't block me!

So even this "discovery" shows only your own negative attitude.

You must be a very sad person. I pray for your soul.

@FullStackAlex
Copy link

FullStackAlex commented Aug 15, 2019

One more thing though:

like everyone owes him

Shopware is a f*cking expensive eCommerce-System. So when I develop(ed) for my clients shops based on their system they get/got a huge amount of money flowing in their ecosystem thanks to me. So, yes! they owe me a lot even from your limited perspective!

@FullStackAlex
Copy link

FullStackAlex commented Aug 15, 2019

Furthermore you still didn't provide any proofs you have improved the package somehow significantly. I went a couple of weeks ago through 4-5 of the last commits in your repo and I could find only updates of the dependency version numbers, no development work at all. Also you didn't answer why you didn't fork the original repo but has uploaded it as an autonomous repo? Maybe so one can't easily track the changes you made on the original source code?

@larixer
Copy link
Author

larixer commented Aug 15, 2019

My changes to the source code can be tracked easily, since the original mocha-webpack git history retained in mochapack. I'm not obliged to dedicate all my time to the development of mocha-webpack fork, I do what I can, I participate in development of many open source packages. If you can dedicate more time to mocha-webpack you are free to make your own fork and maintain it better. I will be glad if someone maintain mocha-webpack better then me, I have lots of other projects that I want to develop. I have started to maintain mocha-webpack fork, because no one else stepped in and I didn't promise any more development then just security updates and accepting pull requests:
#289

@FullStackAlex
Copy link

FullStackAlex commented Aug 15, 2019

Wow, so you actually can talk/write without insulting. Very good.

I understand that one wants to get some recognition or/and appreciation for some open source work. But again in my opinion it's also a burden you carry with you. Your package is now even used in vue-cli, man! (Edit 1: oops, wrong info - don't know how I came up with this 😬 npm doesn't show this vue-cli as dependent; Edit 2: ah, no it's in fact used by vue-cli according to Github dependents tracker) And my personal opinion is that how you handle this issue here isn't what I understand as a good maintenance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants