[BUG] Error: ENOENT: no such file or directory, open '/var/bin/chromium.br'

[MarceloEmmerich]

Environment

• chromium Version: 108
• puppeteer-core Version: 19.3.0
• Node.js Version: 14.x and 16.x
• Lambda nodejs14.x and nodejs16.x -->

Expected Behavior

adding the layer and launching the browser works

Current Behavior

2022-12-01T20:25:16.992Z	83285b39-c65f-4d14-99ab-cbecd1546d68	ERROR	[Error: ENOENT: no such file or directory, open '/var/bin/chromium.br'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/var/bin/chromium.br'
}

Steps to Reproduce

• build the zip file lie described here: https://github.com/Sparticuz/chromium#aws-lambda-layer
• double-checked the ZIP is good (it is, contains "nodejs/node_modules"
• project has puppeteer-core as prod dep
• project has @sparticuz/chromium as dev dep
• deployment with CDK
• lambda code:

exports.handler = async (event: any) =>  {

  console.log(event);

  try {
    const browser = await puppeteer.launch({
        args: chromium.args,
        defaultViewport: chromium.defaultViewport,
        executablePath: await chromium.executablePath,
        headless: chromium.headless,
        ignoreHTTPSErrors: true,
    });
    return browser;
  } catch (err) {
    console.error(err);
  }
  return ''
}

-->

Possible Solution

[MarceloEmmerich]

Well, found the problem after digging some more. What happens is that the layer places files inside the lambda at /opt/nodejs/node_modules/, so for example the chromium.br ends up in /opt/nodejs/node_modules/@sparticuz/chromium/bin/chromium.br.

Now the code for the function executablePath searches elsewhere:

static get executablePath(): Promise<string> {
    if (existsSync('/tmp/chromium') === true) {
      for (const file of readdirSync('/tmp')) {
        if (file.startsWith('core.chromium') === true) {
          unlinkSync(`/tmp/${file}`);
        }
      }

      return Promise.resolve('/tmp/chromium');
    }

    const input = join(__dirname, '..', 'bin');
    const promises = [
      LambdaFS.inflate(`${input}/chromium.br`),
      LambdaFS.inflate(`${input}/swiftshader.tar.br`),
    ];

    if (/^AWS_Lambda_nodejs(?:10|12|14|16|18)[.]x$/.test(process.env.AWS_EXECUTION_ENV) === true) {
      promises.push(LambdaFS.inflate(`${input}/aws.tar.br`));
    }

    return Promise.all(promises).then((result) => result.shift());
  }

The problem is this:

const input = join(__dirname, '..', 'bin');

__dirname for some lambda deployments is /var/task/, so the above line yields /var/bin/chromium.br, which does not exist, at least not for all types of lambda deployments.

Quick Fix proposal: refactor executablePath like this:

static get executablePath(): Promise<string> {
    if (existsSync('/tmp/chromium') === true) {
      for (const file of readdirSync('/tmp')) {
        if (file.startsWith('core.chromium') === true) {
          unlinkSync(`/tmp/${file}`);
        }
      }

      return Promise.resolve('/tmp/chromium');
    }

    let input = '';
    __dirname === '/var/task' ? input = '/opt/nodejs/node_modules/@sparticuz/chromium/bin' : input = (0, path_1.join)(__dirname, "..", "bin");
    const promises = [
      LambdaFS.inflate(`${input}/chromium.br`),
      LambdaFS.inflate(`${input}/swiftshader.tar.br`),
    ];

    if (/^AWS_Lambda_nodejs(?:10|12|14|16|18)[.]x$/.test(process.env.AWS_EXECUTION_ENV) === true) {
      promises.push(LambdaFS.inflate(`${input}/aws.tar.br`));
    }

    return Promise.all(promises).then((result) => result.shift());
  }

[nguyentoanit]

Same issue here:

Node.js version: 16.6.0

package.json:

{
  "dependencies": {
    "puppeteer-core": "19.3.0",
  },
  "devDependencies": {
    "@sparticuz/chromium": "108.0.3",
  }
}

And a lambda layer.

Error message:

{
  "type": "Error",
  "message": "ENOENT: no such file or directory, open '/var/bin/chromium.br'",
  "stack": "Error: ENOENT: no such file or directory, open '/var/bin/chromium.br'",
  "errno": -2,
  "code": "ENOENT",
  "syscall": "open",
  "path": "/var/bin/chromium.br"
}

Lambda code:

import chromium from '@sparticuz/chromium'
import puppeteer from 'puppeteer-core'

puppeteer.launch({
  executablePath: await chromium.executablePath,
  args: chromium.args,
  defaultViewport: chromium.defaultViewport,
  headless: chromium.headless,
  ignoreHTTPSErrors: true,
})

[avegao]

Another one here

[avegao]

With the new version v109.0.0 still failing

[jdahdah]

Is there any way to work around this? Getting this error in a Netlify function and totally blocked right now.

[AdScoops]

I had this issue at one point when packaging my lambda with webpack.

my solution: use webpack externals to mark "@sparticuz/chromium" as an external dependency. Without this webpack will still package this code meaning that the directory resolution was having issues.

[avegao]

Is there any way to work around this? Getting this error in a Netlify function and totally blocked right now.

@jdahdah I only can copy the code provided by @MarceloEmmerich to replace the function executablePath() and remember to copy the class LambdaFS. With this work around (ñapa as we said in Spanish) I can run this package.

[MisterJimson]

I get path_1 is not defined when I try to use @MarceloEmmerich's replacement code

[Sparticuz]

#18 will fix this, help wanted

[MarceloEmmerich]

Happy to help on #18, however I think there is a difference in the use case. #18 reads as we should be able to explicitly pass the location of the brotli files, in other words, a scenario where we know exactly where these reside. This should not be the standard case IMHO. The standard case should remain as it is today, it just needs to check one more "default" location to automatically work with more deployment mechanisms. Having known alternative locations is of course a cool feature to have for the reasons mentioned in #18 .

[Sparticuz]

Agree, I'm not sure the performance implications of having multiple locations to check though. Testing would need to be done to insure the already pretty slow chromium doesn't get even slower because of that.

[FreddieFruitSticks]

Question, how does this work with containerised Typescript lambdas? https://docs.aws.amazon.com/lambda/latest/dg/typescript-image.html. I am noticing that I only get this error when I use the example in to aws doc. When I look inside the docker container I find no chromium.br file.

This is the aws doc reference example - has anyone gotten this to work with chromium?