-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Post Node 14: Replace tape
with node:test
?
#277
Comments
What are the advantages to use There are also |
I would say that I myself use |
Similar move: hypercore-protocol/hypercore-next#39 |
Brittle seems very new and only have ~90 weekly downloads compared to ~640,000 for tape. Doesn't have to mean anything if the later is getting actively maintained, but could potentially be smart to hold on for a little while... I myself also use edit: actually, I see no problems with switching right away actually, seems like other projects are doing it and it only affects our tests |
My impression was that more repositories was about to move to it, but I see now that there aren't that many 🤔 https://github.com/davidmarkclements/brittle/network/dependents?dependent_type=REPOSITORY |
Found the thread I remembered on Twitter with eg. @mcollina: https://twitter.com/matteocollina/status/1447973242581524486 |
I cannot move any of my repositories until I have to support Node v12. |
@mcollina But you will after Node 12 has left LTS in about six months time? |
I'll start testing/using it with smaller repos first and then slowly migrate. The integrated runner with the additional code coverage tool based on c8 is likely worth the switch from tape & tap. |
tape
with brittle
?tape
with node:test
?
I would suggest going with |
tape
with node:test
?tape
with node:test
?
+1 on moving to a runtime solution though I don't have the bandwidth to do it myself. |
For reference, I did this over here for another project: yikesable/fastify-acl@7871e87 |
It was a long time since
tape
received any updates andbrittle
has emerged as the new TAP test framework "for modern times"node:test
is now included with Node.js itself and makes sense to use.I would suggest moving to
brittle
node:test
once we drop support for Node 12.The text was updated successfully, but these errors were encountered: