5 ms·

Could be nice but I'll be avoiding parcel like the plague after being confronted by its complete lack of maintenance of parcel v1 while v2 is in beta, and not t

Could be nice but I'll be avoiding parcel like the plague after being confronted by its complete lack of maintenance of parcel v1 while v2 is in beta, and not the working kind of beta, the broken kind, while the solution to old problems is "use parcel 2" (https://github.com/parcel-bundler/parcel/issues/5695 https://github.com/parcel-bundler/parcel/issues/5695 https://github.com/parcel-bundler/parcel/issues/5294 https://github.com/parcel-bundler/parcel/issues/5294) . In the end I replaced parcel with webpack, less sexy but it's kind of the standard.

jjeaff 5y ago
Ya, we are having the same problem. V1 has some broken parts, but so does V2 and documentation is sparse.
Baconinus 5y ago
There's a roadmap section saying explicitly that they're not RC yet: https://v2.parceljs.org/blog/beta3/#roadmap https://v2.parceljs.org/blog/beta3/#roadmap So it was expected that they would be breaking stuff on their way. I would rather say "I'll keep an eye on Parcel until it becomes stable".
- deleted 5y ago
  [deleted]
- Omin 5y ago
  This information shouldn't be hidden in some document, it should be one of the first things they tell you about in their README and through their versioning (0.1 and 0.2 instead of 1.0 and 2.0).
devongovett 5y ago
Sorry about that. It's difficult to maintain effectively two large open source projects like this simultaneously, especially since this is a side project for most of us. We've probably dropped the ball a little, especially since v2 has taken a long time to build. But the good news is we are getting very close. Docs and migration guides are our main priorities next.
- andrewmcwatters 5y ago
  You don't have to be sorry, you're providing a high quality open-source product for free. It just is what it is. Addendum: I manage a very small open-source product (https://www.planimeter.org/grid-sdk/ https://www.planimeter.org/grid-sdk/), and when you're creating something that competes with an established incumbent, all you can do is your best and focus on the most impactful features. Individuals like the one above saying things like, "I'll be avoiding parcel like the plague," is really disheartening, but try and focus on their concerns more than the actual words they use. Frustrated people are a goldmine for feedback that many projects simply do not receive. Take it in stride, know that you have something others do not, and use it to your advantage. It can be hard to separate your feelings from the words used, but there are diamonds there.
  - danenania 5y ago
    Great comment. I think this applies for pretty much all products or projects, especially in their early stages. There will always be people who don’t get it or have different priorities. It’s ok. When I showed people early versions of EnvKey[1], it felt like half loved it and half thought it was completely pointless. /shrug. At the time I found it discouraging, but now I see that getting even a single person to genuinely love what you’ve built is a major accomplishment and a really good sign that you’re on the right track. If you can find one, you can find ten. If you can find ten, you can find a hundred. And so on. It’s also extremely important to remember that the opposite of love is not hate, negativity, or criticism. It’s indifference. Harsh critics can become some of your best users/customers/advocates if you’re able to learn from them and win them over. 1 - https://www.envkey.com https://www.envkey.com
  - eloff 5y ago
    That's a healthy attitude, I'll try to remember that one next time I get harsh feedback. It's tough to separate my ego from my work.
  - swyx 5y ago
    for what its worth i think adobe pays devon to work on tooling (parcel and react aria|spectrum) somewhat full time and he even has a team around him. but no doubt its just extraordinarily hard to do regardless
dmix 5y ago
This is why it's dangerous using cutting edge software. All in all if they have a small team I'd also point them to v2 for a fixed problem. Rather than backport to some beta version. (Not giving Parcel zero blame in how ready they present themselves).
rowanG077 5y ago
Both issues you linked are about upgrading to newer versions. For these kind of issues saying use the new version is completely fine. There were no security risk. No bug that something essential isn't working. It literally please update the software so a new version of some dependency is supported. I would have done the same.
maxwellwhite 5y ago
> Could be nice but I'll be avoiding parcel like the plague after being confronted by its complete lack of maintenance of parcel v1 while v2 is in beta, and not the You beat me to it here; it’s a shame. That was my experience, too.

jjeaff 5y ago

Ya, we are having the same problem. V1 has some broken parts, but so does V2 and documentation is sparse.

Baconinus 5y ago

There's a roadmap section saying explicitly that they're not RC yet: https://v2.parceljs.org/blog/beta3/#roadmap https://v2.parceljs.org/blog/beta3/#roadmap So it was expected that they would be breaking stuff on their way. I would rather say "I'll keep an eye on Parcel until it becomes stable".

deleted 5y ago
[deleted]
Omin 5y ago
This information shouldn't be hidden in some document, it should be one of the first things they tell you about in their README and through their versioning (0.1 and 0.2 instead of 1.0 and 2.0).

devongovett 5y ago

Sorry about that. It's difficult to maintain effectively two large open source projects like this simultaneously, especially since this is a side project for most of us. We've probably dropped the ball a little, especially since v2 has taken a long time to build. But the good news is we are getting very close. Docs and migration guides are our main priorities next.

andrewmcwatters 5y ago
You don't have to be sorry, you're providing a high quality open-source product for free. It just is what it is. Addendum: I manage a very small open-source product (https://www.planimeter.org/grid-sdk/ https://www.planimeter.org/grid-sdk/), and when you're creating something that competes with an established incumbent, all you can do is your best and focus on the most impactful features. Individuals like the one above saying things like, "I'll be avoiding parcel like the plague," is really disheartening, but try and focus on their concerns more than the actual words they use. Frustrated people are a goldmine for feedback that many projects simply do not receive. Take it in stride, know that you have something others do not, and use it to your advantage. It can be hard to separate your feelings from the words used, but there are diamonds there.
- danenania 5y ago
  Great comment. I think this applies for pretty much all products or projects, especially in their early stages. There will always be people who don’t get it or have different priorities. It’s ok. When I showed people early versions of EnvKey[1], it felt like half loved it and half thought it was completely pointless. /shrug. At the time I found it discouraging, but now I see that getting even a single person to genuinely love what you’ve built is a major accomplishment and a really good sign that you’re on the right track. If you can find one, you can find ten. If you can find ten, you can find a hundred. And so on. It’s also extremely important to remember that the opposite of love is not hate, negativity, or criticism. It’s indifference. Harsh critics can become some of your best users/customers/advocates if you’re able to learn from them and win them over. 1 - https://www.envkey.com https://www.envkey.com
- eloff 5y ago
  That's a healthy attitude, I'll try to remember that one next time I get harsh feedback. It's tough to separate my ego from my work.
- swyx 5y ago
  for what its worth i think adobe pays devon to work on tooling (parcel and react aria|spectrum) somewhat full time and he even has a team around him. but no doubt its just extraordinarily hard to do regardless

dmix 5y ago

This is why it's dangerous using cutting edge software. All in all if they have a small team I'd also point them to v2 for a fixed problem. Rather than backport to some beta version. (Not giving Parcel zero blame in how ready they present themselves).

rowanG077 5y ago

Both issues you linked are about upgrading to newer versions. For these kind of issues saying use the new version is completely fine. There were no security risk. No bug that something essential isn't working. It literally please update the software so a new version of some dependency is supported. I would have done the same.

maxwellwhite 5y ago

> Could be nice but I'll be avoiding parcel like the plague after being confronted by its complete lack of maintenance of parcel v1 while v2 is in beta, and not the You beat me to it here; it’s a shame. That was my experience, too.