fix(deno): replace deprecated Deno server module with Deno.serve

[reosablo]

Overview

What is it?

• Feature / enhancement
• Bug
• Docs / tests / types / typos

Description

This pull request updates the codebase to use the recommended Deno.serve API for creating HTTP servers, replacing the deprecated serve function from the Deno standard library.

// Before:
import { serve } from "https://deno.land/std@0.192.0/http/server.ts";
serve(/* ... */);

// After:
Deno.serve(/* ... */);

You can find the Deno.serve signature here.

I also replace the docs URL for Deno servers. The former redirects to the latter.

- https://deno.com/manual/examples/http_server
+ https://docs.deno.com/runtime/tutorials/http_server

Use cases and why

The latest serve docs says this is deprecated.

Deprecated
(will be removed after 1.0.0) Use Deno.serve instead.

Deno.serve is available since Deno 1.35 released on July 2023.

The long awaited new web server API, Deno.serve(), is now stable. It offers a much easier API while significantly enhancing performance.

Checklist:

• My code follows the developer guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• Added new tests to cover the fix / functionality

[netlify]

👷 Deploy request for qwik-insights pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	b9385cd

[reosablo]

The console outputs unavailable URL http://localhost:3009/app/ (404 Resource Not Found).
This doesn't seem to be a regression bug.

$ npm run serve

> serve
> deno run --allow-net --allow-read --allow-env server/entry.deno.js

Server starter: http://localhost:3009/app/
Listening on http://localhost:3009/

[gioboa]

That's amazing @reosablo you rock
We really appreciate your help ☺️❤️