The Deno team has a big incentive to push for support or contribute to the NestJS project to enable it. Most of the frameworks available on Deno right now are either express or NextJS clones which means that the developer experience is dogwater. If you want to develop a large-scale backend app, then you'll need better tooling and for TS to be the defacto in your codebase, and ofc you'll need DI. Only NestJS provides DI and all of other features combined on Node, but none for Deno. I mean there's Danet, but I feel that it'll end up like DestJS. So yeah, Ryan if you ever read this, give us NestJS-style DI (constructor / method injection) or Bun will win forever.
Hi! Do you recommend Hono over a Deno-only implementation of a REST API server? I followed a tutorial the other day that just used Deno's inbuilt server features and it worked a treat. I'm trying to unblur the line of what all I could/should use Deno and its standard library for vs. bringing in other packages/libraries/frameworks! Thanks so much for the tutorial; I'm really enjoying Deno thus far. =)
It's totally up to you and what your goals are! Each has its pros and cons. Hono is nice because it comes with a bunch of middleware so you can get started easily, but rolling your own is fine too, since you get to minimize your dependencies.
Hono is the best choice today as a router. If you have a small API you will not see a difference. But when your API grows, you will see great router and middleware; sub-applications performance. Just as with everything: Try, learn, earn and joy balance.
@@PavelLang Thanks for the recommendation tbh, I was going to roll my own framework but the world could use 1 less Js framework 🤣. As much as I love PHP I have to say Deno, is giving Laravel a run for its money.
even though it’s catered more to Deno Deploy, I would really love to have more clarity on how to deploy this exact stack to AWS Lambda - tried the official guide but Hono is unable to get the proxied HTTP request from the API Gateway. Deno is just so suitable for lambdas that I would really love to adopt it for everything lambda related 😃
Yes, Deno is trying to be as Web standards compliant as possible. The saddest thing is that someone might actually get the idea to use this (localStorage API) in real backend applications....
The localStorage API in Deno stores data in a specific location under the user's home directory: - On Windows: %USERPROFILE%\AppData\Local\Deno\localStorage - On macOS: ~/Library/Deno/localStorage - On Linux: ~/.local/share/deno/localStorage It should be noted: 1. The implementation of localStorage in Deno is based on the file system. 2. Data is stored in files separately by domain name. 3. The default maximum storage limit for each domain name is 10MB. 4. This storage is persistent, and the data still exists after restarting Deno.
The localStorage API in Deno stores data in a specific location under the user's home directory: - On Windows: %USERPROFILE%\AppData\Local\Deno\localStorage - On macOS: ~/Library/Deno/localStorage - On Linux: ~/.local/share/deno/localStorage It should be noted: 1. The implementation of localStorage in Deno is based on the file system. 2. Data is stored in files separately by domain name. 3. The default maximum storage limit for each domain name is 10MB. 4. This storage is persistent, and the data still exists after restarting Deno.
We used localStorage as an example for this tutorial. In the real world, one might do it for prototyping /caching purposes. But for production use case we suggest using a database or other durable persistent data storage.
@@deno_land ok perfect, now that's clear. But I think you should mention that in the docs when an API is not for production but jsut for testing and playing
Can somebody explain to me how this works in production. I'm coming from PHP, Nginx setup on FreeBSD.... My understanding is that 1.) I need to have deno installed on my freeBSD server, and running as a background process? 2.) I need to configure deno to serve the hono application? 3.) configure cloudflare DNS ?
Day 15 of waiting for NestJS support 🙏
It should just work. Deno supports Node
@@Iammrunkownwell it doesn’t and it is because of all the funky reflection things Nest does with its decorators
@@avwie132 Yeah, that could be the case. I recommend reporting the issues
@@Iammrunkown it isn’t something Deno can solve but what NestJS should solve. And they’ve indicated that they don’t support Deno
The Deno team has a big incentive to push for support or contribute to the NestJS project to enable it. Most of the frameworks available on Deno right now are either express or NextJS clones which means that the developer experience is dogwater. If you want to develop a large-scale backend app, then you'll need better tooling and for TS to be the defacto in your codebase, and ofc you'll need DI. Only NestJS provides DI and all of other features combined on Node, but none for Deno. I mean there's Danet, but I feel that it'll end up like DestJS. So yeah, Ryan if you ever read this, give us NestJS-style DI (constructor / method injection) or Bun will win forever.
Nice video, would be nice a video about how to deploy using both options mentioned at the end 🦕
Coming soon!
When can we see support for Sveltekit
Love me some Svelte
Soon!!
Hi! Do you recommend Hono over a Deno-only implementation of a REST API server? I followed a tutorial the other day that just used Deno's inbuilt server features and it worked a treat. I'm trying to unblur the line of what all I could/should use Deno and its standard library for vs. bringing in other packages/libraries/frameworks! Thanks so much for the tutorial; I'm really enjoying Deno thus far. =)
It's totally up to you and what your goals are! Each has its pros and cons. Hono is nice because it comes with a bunch of middleware so you can get started easily, but rolling your own is fine too, since you get to minimize your dependencies.
Hono is the best choice today as a router.
If you have a small API you will not see a difference.
But when your API grows, you will see great router and middleware; sub-applications performance.
Just as with everything: Try, learn, earn and joy balance.
@@PavelLang Thanks for the recommendation tbh, I was going to roll my own framework but the world could use 1 less Js framework 🤣. As much as I love PHP I have to say Deno, is giving Laravel a run for its money.
even though it’s catered more to Deno Deploy, I would really love to have more clarity on how to deploy this exact stack to AWS Lambda - tried the official guide but Hono is unable to get the proxied HTTP request from the API Gateway. Deno is just so suitable for lambdas that I would really love to adopt it for everything lambda related 😃
which guide did you try? we will make an updated tutorial soon and want to make sure it covers all of your questions!
nice, thank you!
What happens on deno deploy in the free version when the 1M request are reached?
Am i too tired or is local storage being used on server 😮
Yes, Deno is trying to be as Web standards compliant as possible. The saddest thing is that someone might actually get the idea to use this (localStorage API) in real backend applications....
I was thinking that somebody is trolling me in this video.
The localStorage API in Deno stores data in a specific location under the user's home directory:
- On Windows: %USERPROFILE%\AppData\Local\Deno\localStorage
- On macOS: ~/Library/Deno/localStorage
- On Linux: ~/.local/share/deno/localStorage
It should be noted:
1. The implementation of localStorage in Deno is based on the file system.
2. Data is stored in files separately by domain name.
3. The default maximum storage limit for each domain name is 10MB.
4. This storage is persistent, and the data still exists after restarting Deno.
where did the Cs coming from?????
Ok but does it scale?
🪜
What do you mean ?
You can use it, scale it like all api servers no ?
Yes, let's fracture the JS ecosystem even further
Wait a sec, localStorage on the server? What is this? Why is that? What are the use cases?
I'm so confused
The localStorage API in Deno stores data in a specific location under the user's home directory:
- On Windows: %USERPROFILE%\AppData\Local\Deno\localStorage
- On macOS: ~/Library/Deno/localStorage
- On Linux: ~/.local/share/deno/localStorage
It should be noted:
1. The implementation of localStorage in Deno is based on the file system.
2. Data is stored in files separately by domain name.
3. The default maximum storage limit for each domain name is 10MB.
4. This storage is persistent, and the data still exists after restarting Deno.
@@MichaelJiang-fj8kg thanks for the infos, what are the sue cases ?
We used localStorage as an example for this tutorial. In the real world, one might do it for prototyping /caching purposes. But for production use case we suggest using a database or other durable persistent data storage.
@@deno_land ok perfect, now that's clear. But I think you should mention that in the docs when an API is not for production but jsut for testing and playing
Can somebody explain to me how this works in production. I'm coming from PHP, Nginx setup on FreeBSD.... My understanding is that 1.) I need to have deno installed on my freeBSD server, and running as a background process? 2.) I need to configure deno to serve the hono application? 3.) configure cloudflare DNS ?
you use the command "deno run ..." which will start the process. Deno isn't a background process that you configure, you use it as a cli command
what about graphQL
Stay tuned!
make a nestjs tutorial, it's what everyone wants to use not hono.
Stay tuned!
@@deno_land cool 😎
LocalStorage 😮. I'm missing something
It's web standard!
@deno_land yeah, but on the server? It's my first time seeing it 😅
Sankyouuu