Add initial config for Vercel #535
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/jsperf/jsperfcom/9pwjz15y5 |
… security issue by using @npmcorp namespace
…" when using Gulp 4
|
Where we are at:
|
| "cloud": "v2" | ||
| }, | ||
| "alias": "jsperf.com", | ||
| "alias": ["jsperf.com"], |
There was a problem hiding this comment.
alias and name are deprecated, they can be removed from vercel.json
Instead, you should add the production domain to your Vercel Project in the dashboard.
vercel.prod.json
Outdated
| "public": true, | ||
| "alias": ["jsperf.com"], | ||
| "env": { | ||
| "NODE_ENV": "production", |
There was a problem hiding this comment.
You don't need another config file here if you're only changing env vars.
Instead, use the project settings to configure different values for Preview vs Production.
https://vercel.com/blog/environment-variables-ui
Furthermore, if you are only using NODE_ENV, for your serverless functions, then you shouldn't need to assign this at all.
…ky-markdown so hapi/lab can find it. Change .nvmrc to match new version of node for Vercel
|
I need jsperf, how can I help to bring it back up quickly? |
asilluron
force-pushed
the
feature/vercel
branch
from
a8ff603 to
de56c7d
Compare
closes #534