[Rauchg]

That never stopped working. Neither on the edge side (as your live site indicates, which has been edge cached for 109 days in San Francisco), or on the deployment site, as the example below shows:

Try it out: https://hi-there.vercel.app

  ▲  /tmp/ mkdir hi-there
  ▲  /tmp/ cd hi-there
  ▲  hi-there/ echo '<h1>hi sillysaurusx</h1>' > index.html
  ▲  hi-there/ vc
  […]
  Inspect: https://vercel.com/rauchg/hi-there [690ms]
  Production: https://hi-there.vercel.app [copied to clipboard] [9s]

In under 10s which includes the project setup and linking prompts. The main difference is that `now` got shorter to `vc`

Happy to hear more feedback on pricing. Please reach out to [e-mail]

[sillysaurusx]

Happy to hear that. It did, at one point -- I am quite certain of this -- but that was years ago.

I think it was in the transition between now and vercel. Back then, `now` had some sort of requirement where it only worked automatically if the folder had a package.json file. A plain index.html file required configuration. Delighted to see that this is no longer the case.

I'll give `vc` a shot.

The pricing issues stemmed from the fact that I use updown.io to monitor my domains. Since it pings them every 15 minutes or so, and since vercel spins up servers on demand, that means I was paying for essentially 24/7 service, which was an unwelcome bill over what I signed up for. Customer support gave a 50% refund, which I appreciated, and I've downgraded to a free account ever since.

[mushyhammer]

Sorry Guillermo but you’re not being truthful here. “$ now” worked on any node server, not just static content, it would just run “npm start”. Now v2+ instead requires a handler-based approach.

[Rauchg]

I think I misunderstood his comment. I focused on the `index.html` example, but I think he was talking about servers (thanks for pointing that out). That said, the transition was good for servers too depending on what you were using. For example, `package.json` with Next.js was completely seamless!