Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Playground] Broken Stackblitz playground #2891

Open
yhnavein opened this issue Nov 19, 2024 · 1 comment
Open

[Playground] Broken Stackblitz playground #2891

yhnavein opened this issue Nov 19, 2024 · 1 comment

Comments

@yhnavein
Copy link

yhnavein commented Nov 19, 2024

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-world

Describe the bug

Clicking Play online opens Stackblitz that:

  • after change to the source results in a rebuilt that in every second case is broken and un-runnable (as on the screenshot attached)
  • has a lot of Typescript issues, that does not prevent app from running
  • does not explain what Nitro project is trying to solve or accomplish.

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

Zrzut ekranu 2024-11-19 o 12 44 03

Logs

No response

@markthree
Copy link
Contributor

markthree commented Nov 20, 2024

@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.

image

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 🤣)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants