Intlayer + NextJS custom server does not work. (AsyncLocalStorage issues)

[BjornHMS]

I figured I'd post this here, incase anyone else has the same trouble I had.

I am using Next with a custom server. As soon as I added Intlayers to the project Next didn't want to start.

c:\repos\project\node_modules\next\dist\server\app-render\async-local-storage.js:44 throw sharedAsyncLocalStorageNotAvailableError; ^ Error: Invariant: AsyncLocalStorage accessed in runtime where it is not available at Object.<anonymous>

I found a solution through this comment for turborepo .. though unrelated .. I don't even use that package.
vercel/turborepo#3319 (comment)

And then started my server somewhat like this.

const { asyncLocalStorage } = require('./asyncStorage.mjs');
import { createServer } from 'node:http';
import express from 'express';
const app = next({ dev, conf: nextConfig, customServer: true });
const handler = nextApp.getRequestHandler();

nextApp.prepare().then(() => {
  const app = express();

  app.all('*', (req, res) => {
    return asyncLocalStorage.run(new Map(), () => {
      return handler(req, res);
    });
  });

  const httpServer = createServer(app);

  httpServer
    .once('error', (err) => {
      console.error(err);
      process.exit(1);
    })
    .listen(3000);
});

Maybe you can fix it so this is unnecessary .. either way I hope this solution helps someone.

[aymericzip]

Thanks @BjornHMS

Can you share your server code before the fix to reproduce ?

[BjornHMS]

Thanks @BjornHMS

Can you share your server code before the fix to reproduce ?

Pretty much the same, but without context bootstrapping AsyncLocalStorage

import { createServer } from 'node:http';
import express from 'express';
const app = next({ dev, conf: nextConfig, customServer: true });
const handler = nextApp.getRequestHandler();

nextApp.prepare().then(() => {
  const app = express();

  app.all('*', (req, res) => {
     return handler(req, res);
  });

  const httpServer = createServer(app);

  httpServer
    .once('error', (err) => {
      console.error(err);
      process.exit(1);
    })
    .listen(3000);
});

[BjornHMS]

I should also note that, when running Next from a custom server like this, Intlayer does not build the .intlayer folder.
Which then downstream causes this error

 ⨯ ./node_modules/intlayer/dist/esm/index.mjs:2:1
Module not found: Can't resolve '@intlayer/config/built'
  1 | import { Locales, Locales as Locales$1 } from "@intlayer/types";
> 2 | import configuration from "@intlayer/config/built";
    | ^
  3 | import { Intl, compact, cond, currency, date, enu, gender, getBrowserLocale, getDictionary, getEnumeration, getEnumeration as getEnumerationContent, getHTMLTextDir, getIntlayer, getLocaleFromPath, getLocaleLang, getLocaleName, getLocalizedUrl, getMarkdownMetadata, getMultilingualUrls, getNesting, getPathWithoutLocale, getTranslation, getTranslation as getTranslationContent, insert, localeFlatMap, localeMap, localeRecord, md, nest, number, percentage, relativeTime, t, units } from "@intlayer/core";
  4 | import { file } from "@intlayer/core/file";
  5 |

https://nextjs.org/docs/messages/module-not-found

And running npx intlayer build --width "yarn dev" throws an error

C:\Repos\project\node_modules\intlayer\node_modules\@intlayer\chokidar\dist\cjs\utils\runParallel.cjs:108
                        else reject(Object.assign(/* @__PURE__ */ new Error("Parallel process failed"), {
                                                                  ^

Error: Parallel process failed
    at ChildProcess.<anonymous> (C:\Repos\mapRefactor\node_modules\intlayer\node_modules\@intlayer\chokidar\dist\cjs\utils\runParallel.cjs:108:46)
    at ChildProcess.emit (node:events:519:28)
    at ChildProcess._handle.onexit (node:internal/child_process:293:12) {
  code: 1,
  signal: null
}

[BjornHMS]

Building first and then running watch in parallel does work npx intlayer build && npx intlayer watch --with "yarn dev"
It does error when you terminate the task though .. I'm guessing that's just a false positive though

Terminate batch job (Y/N)? Terminate batch job (Y/N)?

C:\Repos\mapRefactor\node_modules\intlayer\node_modules\@intlayer\chokidar\dist\cjs\utils\runParallel.cjs:108
                        else reject(Object.assign(/* @__PURE__ */ new Error("Parallel process failed"), {
                                                                  ^

Error: Parallel process failed
    at ChildProcess.<anonymous> (C:\Repos\mapRefactor\node_modules\intlayer\node_modules\@intlayer\chokidar\dist\cjs\utils\runParallel.cjs:108:46)
    at ChildProcess.emit (node:events:519:28)
    at ChildProcess._handle.onexit (node:internal/child_process:293:12) {
  code: 1,
  signal: null
}

Node.js v22.21.1

[BjornHMS]

Building first and then running watch in parallel does work npx intlayer build && npx intlayer watch --with "yarn dev"
It does error when you terminate the task though .. I'm guessing that's just a false positive though

This is not a good long term solution, due to the error when terminating the task. The process stays in memory thus keeping the port from being released. This also keeps the watch task from stopping. I only noticed since I started getting "compiled" in my terminal mysteriously afterwards.

I have since opted for using npm-run-all
npx intlayer build && npm-run-all --parallel intlayer:watch start:dev
And that seems to let me build, watch and run my server without fault.

[aymericzip]

Thanks for reporting @BjornHMS

I reworked the process, you would be able to remove npm-run-all for the 7.0.4-canary.0

Let me know if it fix it

[BjornHMS]

Thanks for reporting @BjornHMS

I reworked the process, you would be able to remove npm-run-all for the 7.0.4-canary.0

Let me know if it fix it

Ok cool will do.
Did you fix both? or did you mean specifically the problems with runParallel?

[aymericzip]

I reworked how runParallel terminate the parallel program, that should fix the false positive you mentioned, and the process that stay in memory

Let me know if I'm missing out something else

Note, I'm not on windows, so I might miss some side effects, but I reused the logic of npm-run-all so I'm confident that it will work