This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update all non-major dependencies (@cloudflare/workers-types, @scalar/api-reference, miniflare, node, pnpm, undici)

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update devdependency @azure/functions to v4
• chore(deps): update devdependency firebase-functions to v5

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Environment

NodeJS version : 14.16.2
Nitropack : 0.2.2

Reproduction

• Install the library "pg" (e.g : npm i pg)
• Use import { Pool } from 'pg' in a route

Describe the bug

I have a problem when trying to import Pool from 'pg', a postgres library to connect to a postgres database.

I get the following error :

SyntaxError: Named export 'Pool' not found. The requested module 'file:///project_root/node_modules/.pnpm/[email protected]/node_modules/pg/lib/index.js' is a CommonJS module, which may not support all module.exports as named exports.

Nitro then make the recommandation to use use the default export, however it still doesn't work, I get a typescript error : Module pg has no default export.

Is there a way to get around the problem ? If no do you know any esm library for postgres ?

Additional context

No response

Logs

No response

• nuxt/framework#3399

Dev server uses isolated worker threads. This prevents having shared cache that is preserved across reloads

nuxt/nuxt#12780

Alternatively we can integrate with route caching rules for single preset

nuxt/nuxt#13563

on nuxt3/bridge this leads to a 'Not ready!' being rendered rather than the initial page

Rework changes of nuxt/framework#1334

https://vercel.com/docs/build-output-api/v3

nuxt/framework#3153

• RFC
• POC

https://www.stormkit.io/

nuxt/nuxt#13341

https://firebase.google.com/docs/functions/manage-functions#modify-region

nuxt/nuxt#10959

We can use the new isPublicAssetURL for Cloudflare worker to avoid unnecessary try cache on getAssetFromKV (example usage in service-worker)

When deploying a Nitro app with the azure-functions preset, static Images such as .pngs and .jpgs are rendered incorrectly. (They are converted to string, which messes with their encoding.)

Issues to check:

• is this a limitation of azure functions? (not serving binary files)
• could this be resolved with something similar to #96?

context: nuxt/nuxt#12677

nuxt/nuxt#13138

@danielroe https://nodejs.org/api/packages.html#resolving-user-conditions
currently probably only production and development fall into the category of conditions we'd support out-of-the-box, but the capacity to add more or customise them seems useful

Currently, we do use default module node import and I think it is a viable default but allowing to extend woulnd't be a bad idea either

nuxt/nuxt#11786

Most importantly prerender:route hook which can be useful to modify and inspect pretender results. (eg: for service-worker to inject it's script)

Linked issue: nuxt/nuxt#13448

For now, it's purpose it to export and polyfill global $fetch for Client/Universal builds.

Currently, we have some small dependencies that are only usable for some presets:

• @cloudflare/kv-asset-handler
• @netlify/functions
• archiver (for azure)

Their install size overhead is very small (3.4M non-shared!) but this can be a problem if we are more presets that require such dependencies. Currently we do not include any cli and suggest using npx for tools such as wrangler and miniflare

Once we had the ability to auto-install deps, we can come back to this as check cons/pros.

Also related: nuxt/nuxt#13166

Currently it is broken with pnpm symlinks:

h3 support: unjs/h3#68 is landed for Node.js compatible environments.

We might need to improve unenv mocks as well to universally make stream support available.

Currently waiting for h3 Event API to be completed and especially with Event class we can leverage native web API for sending streams.

#50

nuxt/nuxt#11651

https://github.com/aws-amplify/amplify-hosting

List all possible API routes as / or /_nitro and another runtime state of nitro. This can be initially implemented as a devserver feature.

Use h3 + radix3 for handling API instead of middleware base

Environment

node --version
v16.14.2

Reproduction

https://github.com/X7md/nitropack-test

git clone https://github.com/X7md/nitropack-test
cd nitropack-test
npm install
# there is npm pkg @imagemagick/magick-wasm 

Describe the bug

Try to build using NITRO_PRESET=cloudflare npx nitropack build, but I got this error

Additional context

No response

Logs

<--- Last few GCs --->

[35531:0x5f79840]    15787 ms: Scavenge 2030.8 (2065.6) -> 2028.6 (2066.1) MB, 3.6 / 0.0 ms  (average mu = 0.118, current mu = 0.110) allocation failure 
[35531:0x5f79840]    15794 ms: Scavenge 2031.3 (2066.1) -> 2029.5 (2067.3) MB, 4.6 / 0.0 ms  (average mu = 0.118, current mu = 0.110) allocation failure 
[35531:0x5f79840]    15801 ms: Scavenge 2032.4 (2067.3) -> 2030.4 (2076.3) MB, 4.5 / 0.0 ms  (average mu = 0.118, current mu = 0.110) allocation failure 


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xb09980 node::Abort() [node]
 2: 0xa1c235 node::FatalError(char const*, char const*) [node]
 3: 0xcf784e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xcf7bc7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xeaf465  [node]
 6: 0xeaff46  [node]
 7: 0xebe46e  [node]
 8: 0xebeeb0 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 9: 0xec1da5 v8::internal::Heap::HandleGCRequest() [node]
10: 0xe4f447 v8::internal::StackGuard::HandleInterrupts() [node]
11: 0x11fb805 v8::internal::Runtime_StackGuard(int, unsigned long*, v8::internal::Isolate*) [node]
12: 0x15f0b19  [node]
Aborted (core dumped)```

Adding as a feature to route rules.

Refs:

• #39
• https://github.com/unjs/nitro-poc-layer0 (private)

TODO:

• Move POC as a published preset
• Add deployment guide (@tristanlee85)

Improvements:

• Use direct builder/core API instead of invoking CLI
• Layer0 config
  • Option to set layer0 core/cli version
  • Pin used version on first build to .nitrorc
• Map route rules <> Layer0 router
  • Any reference for JSON format instead of routes.js?
• Map Proxy support (#113) <> Layer0 backends

heroku is very customisable but mostly this is done with buildpacks. Here's the node one.

By default the node buildpack will build, prune dev dependencies + package the entire app folder into a docker image. This is lots more space than Nitro needs. Options:

1. create our own heroku buildpack
2. create docker image (which can be shared with other platforms): #54

If you use the default heroku buildpack, you'll need to run heroku config:set HOST=0.0.0.0

Context: nuxt/nuxt#13586

Relevant upstream improvement: unjs/unenv#23

Environment

NodeJS: 17.19.0
@nuxt/nitro@npm:@nuxt/[email protected]
@nuxt/[email protected]

Reproduction

https://github.com/devind-team/eleden

But its not easy, because it need server.

Describe the bug

This error is related to sockets, when on the client I establish a connection with the server via apollo-subscription.

In console I get:

And the page hangs in an endless reload.

And client does not set cookie. Before, on nuxt 2.5 it worked good.

Additional context

I use apollo subscription.

Logs

No response

Context: nuxt/nuxt#13599

Proposal:

routes: {
  '/public': { cors: true }
}

We probably need an h3 utility for this as well: unjs/h3#82

Environment

Reproduction

(nuxt/nuxt#13748)

Describe the bug

When dev config is set, we need to force using nitro-dev preset

Additional context

No response

Logs

No response

A quick guide in advanced section about preset creation probably and ideally an starter template for POC.

Adding a contribution guide also for steps.

• The issue to ask for preset and platform requirements
• POC with a nitro starter template
• PR with always a named preset and docs section

nuxt/framework#2663

nuxt/nuxt#11747

https://developers.cloudflare.com/workers/cli-wrangler/configuration#modules

Using this, we can natively use imports for chunks instead of using one entry (maybe behind a flag?)

An alternative might be using KV + eval but last time checked both eval and importScripts were forbidden due to security concerns they had. So it is probably the only way to use the native option.

Note: This is not replacing normal workers as is a paid service.

Looks like render.com does not have a separate setup for serverless/edge rendering: https://render.com/docs/web-services.

Setting up render was super-simple, and took only 30 sec. or so from creating an account to connecting the repository. This may just be a documentation task. (It deploys as a node server within a docker container.)

cc: @Atinux

nuxt/nuxt#11428

@danielroe we have server timings for loading chunks but would be nice to know (particularly where we are performing internal $fetch) what the timings for each handler are

Context and how-to are not really clear to me at the moment but we might benefit from more nitro lifecycle hooks to make such a thing possible.

Related unjs/hookable#37

While generating pages, the crawler scans for href="" links (filtering for local and without extension) This is the most straightforward way. We can allow the runtime to hint crawler with HTTP headers to crawl more with a header like X-Nitro-Prerender: link1, link2, ... (the alternative is using standardLink: header with prefetch strategy to infer this)

Usage notes/documentation:

1. Need to add engines.node version to package.json (docs)
2. set HOST to 0.0.0.0

also supports docker images: #54

Supporting deno deploy: https://dash.deno.com/

It is actually almost possible via worker preset! We only need documentation and an official preset.

Environment

Operating System: Linux
Node Version: v17.1.0
Nuxt Version: 3.0.0-27319101.3e82f0f
Package Manager: [email protected]
Bundler: Vite
User Config: -
Runtime Modules: -
Build Modules: -

Reproduction

2. Add server/api/test.ts

import { v4 } from "uuid";

export default () => {
  return v4();
};

Describe the bug

Building the project causes the package uuid to fail to be imported. The problem does not exist when running the dev server.

Cannot find module '/home/me/dev/nuxt3-app/.output/server/node_modules/uuid/wrapper.mjs' imported from /home/me/dev/nuxt3-app/.output/server/chunks/test.mjs
  at new NodeError (node:internal/errors:371:5)  
  at finalizeResolution (node:internal/modules/esm/resolve:394:11)  
  at moduleResolve (node:internal/modules/esm/resolve:915:10)  
  at defaultResolve (node:internal/modules/esm/resolve:1005:11)  
  at ESMLoader.resolve (node:internal/modules/esm/loader:475:30)  
  at ESMLoader.getModuleJob (node:internal/modules/esm/loader:245:18)  
  at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:79:40)  
  at link (node:internal/modules/esm/module_job:78:36)

Additional context

Moved from nuxt/nuxt#13040

Logs

No response

nuxt/nuxt#11779

We can use renderDynamicImport (todo) to load async chunks for server-worker target instead of using one chunk with either fetch+eval or importScripts. This will allow us deploying a real world app (like docus transformers) to static hosting without huge startup time.

Alternative: We can also use experimental ES worker modules (blog) but I think last time there was a chrome only support for this and firefox was unable

expose swagger compatible API from dev server based on handler defenitions.

Environment

• Operating System: macOS
• Node Version: v16.14.0
• Nitro Version: 0.2.1
• Package Manager: [email protected]

Reproduction

n/a

Describe the bug

It would be a nice addition to nitro if there is be a possibility to change the response of static assets. Then it would also be possible to implement content encoding like brotli or gzip.

Additional context

There does exist a discussion in the nuxt repo. https://github.com/nuxt/framework/discussions/3472

In addition to the discussion i already found the corresponding lines, which i changed in nuxt, in the nitro package:

https://github.com/unjs/nitro/blob/main/src/runtime/static.ts#L68
https://github.com/unjs/nitro/blob/main/src/rollup/plugins/public-assets.ts#L44

Logs

No response

Update 21.07.2022

I wrote a module which can handle the compression https://github.com/exreplay/nuxt-compression. This is still no official way and messes with the internal nitro code but there is no need to use patches.

Currently, we have unjs/server-placeholder for dev server that prevents unnecessary service calls. However, this can be useful for production as well. We only need to also ensure it will be configurable before spreading.

Built with node and a minimal generated docker image:

• Default: Only generate Dockerfile
• Build option provided: Try to also build an image using the local docker client CLI (alternative would be a JS client but is too much hassle)
• Compose option provided: Generate basic docker-compose
• Registry option provided: Also push to the register

Note: It might improve heroku preset as well (#49)

Environment

• Operating System: Windows_NT
• Node Version: v16.13.1
• Nuxt Version: 3.0.0-27338323.1e98259
• Package Manager: [email protected]
• Bundler: Vite
• User Config: -
• Runtime Modules: -
• Build Modules: -

Reproduction

https://github.com/AlexDicy/nuxt-min-reproduction

Describe the bug

Moved from nuxt/nuxt#13131

Additional context

No response

Logs

No response

https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html

nuxt/nuxt#11700