This website requires JavaScript.
Explore
Help
Sign In
archive
/
rsnext
Watch
1
Star
0
Fork
You've already forked rsnext
0
Code
Issues
Pull requests
Projects
Releases
Packages
Wiki
Activity
Actions
c254b74c00
rsnext
/
pnpm-workspace.yaml
4 lines
47 B
YAML
Raw
Normal View
History
Unescape
Escape
Update to leverage pnpm for monorepo (#37259) * Update to leverage pnpm for monorepo * update compiled * update stats action * update ci install step * update ci * add test dep * update invoking scripts * update caching * skip cache for now * update dep * update packages and fix babel * update compiled * update lint * update test * update ci * update pnpm store caching * update path for windows * update restore-key config * update caching * remove extra build azure stage * re-add checkout * update setting pnpm store * bump * remove azure caching as pnpm is faster to download * update contributing * apply suggestions * remove install-peers * prepublish -> prepublishOnly * prepublish -> prepublishOnly more * more yarn -> pnpm references * more yarn -> pnpm references take 2 * use workspace protocol for root package.json Co-authored-by: Steven <steven@ceriously.com>
2022-05-29 06:35:16 +02:00
packages
:
-
'packages/*'
misc: add benchmarking script for edge rendering (#40716) This PR adds the benchmarking script I've been using for #40251 to measure the performance improvements that we make to the Edge SSR runtime. This tool: - uploads two version of the benchmarking project to Vercel, one with the latest canary and the one with your current local changes in dist (don't forget to build!) - runs some tests against the published url to measure TTFB - displays a nice chart and table What this doesn't do (yet): - allow you to choose which URL to compare - allow you to change the measured metric - run a battery of differnet test ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` https://user-images.githubusercontent.com/11064311/191270204-04447e20-5a40-43a9-bcda-b7eaeb3d270a.mov ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2022-09-27 17:57:16 +02:00
-
'bench/vercel/'
Reference in a new issue
Copy permalink