learning: working with nitro server

[Drew-Macgibbon]

I am starting to see similarities with express, but I still need to dig deeper to understand how things work and how I can better structure/optimize the code. This will be a running thread of my findings.

I'm breaking down my findings into separate issue threads, each thread will become an article/video.

1. h3event: learning: H3Event object #80
2. middleware: learning: nitro middleware #81
3. utils: learning: nitro utils #82
4. func - unstorage: learning: unstorage #79

[Drew-Macgibbon]

We can use any express package like so:

// middleware/cors.ts
import cors from 'cors';

export default defineEventHandler(({ req, res }) => new Promise((resolve) => cors()(req, res, resolve)));

Or helmet or any express package:

// middleware/helmet.ts
import helmet from 'helmet';

export default defineEventHandler(({ req, res }) => new Promise((resolve) => helmet()(req, res, resolve)));

[Drew-Macgibbon]

Auto-imports

These work the same as client-side auto-imports within your nuxt 3 app.

Example:
directory structure.

server/utils/logger.ts
// preference: I like to name files in sub-folders with the folder as a prefix
server/utils/scraper/scraperBlogs.ts

You can now call logger or scraperBlogs directly if they have a default export.
Named exports are also directly callable.
Let's say the scraperBlogs file has a testFunction named export, yo don't have to prefix it when calling, it can be directly referenced as testFunction()