Pooya Parsa comments

Results 2274 comments of


                                            Pooya Parsa

refactor: update NitroOptions to allow DotenvOptions for dev property

I think we should simply update `nitro dev` (CLI command) to load dot env by default. No need to change other places.

perf: improve JSON signature regex for performance and clarity

Thanks for PR but can you please also share a benchmark diff report against both Node.js and Bun? 🙏🏼 (since this is a security area, i rather to minimize changes...

Manual vercel/nft deoptimization for externals

@hipstersmoothie we are migrating to [nf3](https://github.com/unjs/nf3) can you please open an issue over there? 🙏🏼 (also feel free to contribute, implementing feature is not that hard, we should introduce an...

Manual vercel/nft deoptimization for externals

@vafanassieff do you have a reproduction? please try latest v3 nightly. You do not need to manually specify rules for wasm support (it is bundled by default)

Manual vercel/nft deoptimization for externals

Thanks for repro @vafanassieff. Correct usage of nightly is like this: ```json "nitro": "npm:nitro-nightly@latest" ``` (make sure to remove node_modules and lockfile to avoid stalled deps) --- Unfortunately, the upgrade...

`storage.get(key, { type })`

Validation is another topic (for object/json), these are data types.

Assets file cannot be copied to output public directory

You should use `server/public` when `srcDir` is set to `server` currently. In the future, we might also auto add top level `public` to be similar to Nuxt (#2924)

build: use cjs/mjs extensions for cjs/esm builds

Thanks for sharing this @kazupon. This is off topic just to share, in nuxt 3, we set `__VUE_PROD_DEVTOOLS__` flag to optimal value but since valid `.mjs` could be also externalized...

allow syncing runtime config with full stack frameworks without depending on imports

/cc @rudolfbyker please tell if you like to work on this ❤️

allow syncing runtime config with full stack frameworks without depending on imports

> We need to consider the security implications of exposing user provided variables in the global scope like this. I don't think there is any security concern API lives in...