You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@yhnavein
This is where setting the compatibility date automatically initially reopens a service (on stackblitz) and causes access to be disabled, so you can ctrl + c to disconnect the service and npm run dev to restart it. Of course, there may also be network access issues in this area.
Just start it and wait for nitro entry to build and then refresh it.
On top of that, the type issue is one that stackblitz doesn't support enough, it's buggy, but it's fine in a native development environment.
The last issue comes down to nitro's documentation, which I agree is lacking and is an area for improvement.
in my own use of nitro, I think the key problem that nitro solves is that it allows you to easily and inexpensively run on any serverless service, just by setting up presets to adapt the api service to almost any commercial off-the-shelf serverless service on the market. The end product is also very small in production, unused dependencies are not packaged into the product, and routes are loaded on demand (see this article 👉 nuxt-on-the-edge).
These optimisations make the api faster to cold-start in production, consume fewer resources, and cost less money! (Sometimes it may still be free because the consumption doesn't reach the paid plan and the free plan is sufficient 🤣)
Environment
From production docs site that opens: https://stackblitz.com/github/nitrojs/nitro/tree/main/examples/hello-world
Reproduction
Just click
Play online
button on the main Nitro's page. https://stackblitz.com/github/nitrojs/nitro/tree/main/examples/hello-worldDescribe the bug
Clicking
Play online
opens Stackblitz that:I was expecting to learn what Nitro does, but docs definitely did not help. And
Play online
, apart from being broken does not help neither.Additional context
Logs
No response
The text was updated successfully, but these errors were encountered: