Package Details: web-ext 8.9.0-1

Git Clone URL: https://aur.archlinux.org/web-ext.git (read-only, click to copy)
Package Base: web-ext
Description: A command line tool to help build, run, and test web extensions
Upstream URL: https://developer.mozilla.org/en-US/Add-ons/WebExtensions
Keywords: nodejs, web-ext
Licenses: MPL-2.0
Conflicts: nodejs-web-ext
Provides: nodejs-web-ext
Replaces: nodejs-web-ext
Submitter: arojas
Maintainer: brianwo
Last Packager: brianwo
Votes: 5
Popularity: 0.37
First Submitted: 2025-03-31 20:36 (UTC)
Last Updated: 2025-07-25 14:24 (UTC)

Pinned Comments

Latest Comments

7cff commented on 2025-10-23 23:24 (UTC)

The reason for the unit test failure was because of a bug upstream that caused the tests to fail (and possibly for web-ext to be bugged) on certain versions of Node: https://github.com/mozilla/web-ext/issues/3429

Furthermore, the wiki recommends performing testing specifically so that we can catch these types of bugs during packaging, and if the tests must be disabled, it should be done using one of the listed methods instead of that line you currently have in the PKGBUILD: https://wiki.archlinux.org/title/Creating_packages

neilsimp1 commented on 2025-07-05 20:20 (UTC)

FYI this worked with regular nodejs for me by installing with --skip-dependency-checks.

marcin commented on 2025-05-11 23:40 (UTC)

If you have some dependency issues with node-lts-iron, what helped in my case was to clear yay cache (~/.cache/yay/) and reinstalling.

brianwo commented on 2025-05-06 11:17 (UTC) (edited on 2025-05-06 11:19 (UTC) by brianwo)

@missingSleepDeps

I have updated the package, skipping the test part. It should now build just fine.

After seeing consulting through other nodejs packages, it seems like the test part in unnecessary.

This package should work as how it's being tested upstream by web-ext developer.

missingSleepDeps commented on 2025-05-01 00:08 (UTC) 

575 passing (6s)
  1 pending
  2 failing

  1) config
       loadJSConfigFile
         provides help message on load failure due to .js ESM config file and no package:
     AssertionError: expected promise to be rejected with 'UsageError' but it was fulfilled with { sourceDir: 'fake/dir' }                                          


  2) config
       loadJSConfigFile
         provides help message on load failure due to .js ESM config file and type commonjs package:
     AssertionError: expected promise to be rejected with 'UsageError' but it was fulfilled with { __esModule: true, default: {} }                                  




==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: web-ext-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
web-ext - exit status 4
PAKtC