Steven
Steven
@TooTallNate @EndangeredMassa @trek CI is finally green ✅ Please take another look.
Hi @abriginets What's the use case for this? The linked article mentions "machine learning, modelling, genomics" but these are generally not a good fit for Vercel because they will timeout...
> And when my functions execute faster Vercel gets lighter bills [Serverless Function Execution is billed in GB Hours](https://vercel.com/docs/concepts/limits/overview#typical-monthly-usage-guidelines) meaning that increasing memory will increase usage for the same duration....
Since this is marked as semver-major, lets remove the reading of `.env` and `.env.build` too. That will fix this related issue: - https://github.com/vercel/next.js/issues/17338
There have been some changes since this PR was created. You no longer need to manually add frameworks to Vercel, instead you can update the framework to output `.vercel_build_output`. Learn...
- Related to #261
That `--loglevel=info` is way too verbose. I only want to print the version of npm. And it should be the default behavior, not hidden behind a flag, so it can...
That sounds like a good first step 👍
I would be fine if the version was only printed in CI. Especially if that helps avoid the need of a new log level (because no one will remember to...
I would prefer it print the version for every command because the flags can change between npm versions (for example, `npm exec` changed). And we don't know what the future...