Skip to content
This repository has been archived by the owner on Nov 28, 2020. It is now read-only.

Think about Node library/tool benchmarks #206

Open
bmeurer opened this issue Feb 26, 2018 · 1 comment
Open

Think about Node library/tool benchmarks #206

bmeurer opened this issue Feb 26, 2018 · 1 comment

Comments

@bmeurer
Copy link
Member

bmeurer commented Feb 26, 2018

As brought up in v8/web-tooling-benchmark#33 we don't currently have a place for benchmarks regarding Node libraries/tools, for example @std/esm.

cc @mathiasbynens @jdalton

@davisjam
Copy link
Contributor

davisjam commented Oct 6, 2018

I am working on this as part of #6 / #243, for the use case "Developer tooling: Node.js".

I am currently planning to run a series of npm install's using verdaccio as a proxy.
I am open to incorporating other tools e.g. esm.
I welcome input.

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

No branches or pull requests

2 participants