Package Details: nodejs-web-ext 5.0.0-1

Git Clone URL: https://aur.archlinux.org/nodejs-web-ext.git (read-only, click to copy)
Package Base: nodejs-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
Licenses: MPL2
Submitter: yan12125
Maintainer: yan12125 (lilac)
Last Packager: lilac
Votes: 11
Popularity: 1.50
First Submitted: 2016-07-16 06:03
Last Updated: 2020-07-27 19:11

Latest Comments

1 2 Next › Last »

yan12125 commented on 2020-07-13 15:51

I've solved it:

Great!

Maybe it's a good idea to check if and how this package sets permissions.

I didn't change permissions. Maybe yarn is doing something wierd.

Markus.N commented on 2020-07-13 15:46

I've solved it: it was the permissions.
I've tried to work around by creating a symlink to web-ext/node_modules/source-map in /usr/lib/node_modules but it still did not work. Then I've tried to cat /usr/lib/node_modules/source-map/package.json and got a permission denied. From that moment on it was easy. Just chmod'ed all directories under /usr/lib/node_modules to ugo+rx and all files to ugo+r.

Maybe it's a good idea to check if and how this package sets permissions.

yan12125 commented on 2020-07-13 15:45

Thanks! This line in your log looks suspicious

openat(AT_FDCWD, "/usr/lib/node_modules/web-ext/node_modules/source-map/package.json", O_RDONLY|O_CLOEXEC) = -1 EACCES (Permission denied)

That file on my machine has mode 0644.

Markus.N commented on 2020-07-13 15:25

OK, I've found some difference: On my machine, it switches from /usr/lib/node_modules/web-ext/node_modules/source-map to /usr/lib/node_modules/source-map, while it doesn't on yours.
https://pastebin.com/1117PJhR

BTW ... nice to learn a new tool (never used strace before)

yan12125 commented on 2020-07-13 12:55

Hmm, not sure what happened. How about running this command to see what node.js expects?

strace web-ext lint |& grep source-map

This is what I got: https://cfp.vim-cn.com/cbnlR

Markus.N commented on 2020-07-13 06:17

Thank you for your reply. To know that this combination should work is already helpful. I have removed and reinstalled all nodejs-related packages, unfortunately no change.

web-ext lint

internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module 'source-map'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/web-ext/node_modules/source-map-support/source-map-support.js:1:25)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)

yan12125 commented on 2020-07-13 01:24

I got no "Cannot find module" issues with nodejs-lts-dubnium. Could you paste all error messages?

Markus.N commented on 2020-07-12 17:27

I'm getting Error: Cannot find module 'source-map' when I try any operation (lint, build, sign ...). I suspect it's because I had to downgrade nodejs from erbium to dubnium, but I'm not sure about that. I could even have made a mistake when I reinstalled this package. I removed it completely using pacman -R, then reinstalled using yay and doing a clean build.
I also checked that /usr/lib/node_modules/web-ext/node_modules/source-map exists.

Now I'm a bit lost ...

yan12125 commented on 2019-12-30 12:33

@nicoulaj: Thanks for the feedback. That seems to be related to a upstream bug: https://github.com/mozilla/web-ext/issues/793. I'm in general reluctant to add workarounds for such upstream bugs. Here are some possible ways to install this:

nicoulaj commented on 2019-12-30 11:53

Having WEB_EXT_API_KEY/WEB_EXT_API_SECRET environment variables causes tests to fail, maybe the PKGBUILD could unset it or launch tests in a clean environment ?