Package Details: insomnia 10.2.0-1

Git Clone URL: https://aur.archlinux.org/insomnia.git (read-only, click to copy)
Package Base: insomnia
Description: Cross-platform HTTP and GraphQL Client
Upstream URL: https://github.com/Kong/insomnia
Licenses: MIT
Submitter: kpcyrd
Maintainer: Gobidev
Last Packager: Gobidev
Votes: 23
Popularity: 0.000259
First Submitted: 2020-10-19 17:29 (UTC)
Last Updated: 2024-11-29 12:02 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

kescherAUR commented on 2020-11-05 09:03 (UTC) (edited on 2020-11-05 09:08 (UTC) by kescherAUR)

Executing every single line in the build() function by hand works... So I can just do makepkg -eR and I'll have a working package. Weird.

kescherAUR commented on 2020-11-05 08:51 (UTC) (edited on 2020-11-05 08:52 (UTC) by kescherAUR)

Since the update for this package to use nvm, the package fails in the build() function. More specifically, it fails at the line

source /usr/share/nvm/init-nvm.sh

even though manually sourcing that works fine. I use bash.

sardaukar commented on 2020-11-05 02:20 (UTC) (edited on 2020-11-05 02:24 (UTC) by sardaukar)

Still getting an error on build() - is there a fix?

Running "source /usr/share/nvm/init-nvm.sh" gives me an error I think because I run the fish shell. If I source it on a bash prompt, it works fine.

/usr/share/nvm/nvm.sh (line 922): Unexpected ')' found, expecting '}'
      "${NVM_NODE_PREFIX}")
                          ^
from sourcing file /usr/share/nvm/nvm.sh
    called on line 4 of file /usr/share/nvm/init-nvm.sh
from sourcing file /usr/share/nvm/init-nvm.sh
source: Error while reading file “/usr/share/nvm/nvm.sh”
/usr/share/nvm/bash_completion (line 35): Unexpected ')' found, expecting '}'
      alias) __nvm_installed_nodes ;;
           ^
from sourcing file /usr/share/nvm/bash_completion
    called on line 5 of file /usr/share/nvm/init-nvm.sh
from sourcing file /usr/share/nvm/init-nvm.sh
source: Error while reading file “/usr/share/nvm/bash_completion”

luxcem commented on 2020-11-04 12:14 (UTC)

It might be but there is no guarantee, the nodejs-lts-fermium version is not officially supported. Also nodejs-lts-fermium conflicts with nodejs and I rather not force people to downgrade nodejs to @v14 just for this package. I think nvm is the "cleanest" solution, but not the most efficient.

twnaing commented on 2020-11-04 02:47 (UTC)

nvm affects all the terminals (and it takes time to startup). Wouldn't nodejs-lts-fermium (nodejs 14.x) be more suitable?

luxcem commented on 2020-11-03 11:57 (UTC)

It seems to be an issue with node@v15 as it builds with node@v14. I updated the PKGBUILD to use nvm instead and build it with the supported version.

blallo commented on 2020-11-02 12:10 (UTC)

Like @WhyNotHugo, I am getting an error. The log content is the following

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'app-package' ]
2 info using npm@6.14.8
3 info using node@v15.0.1
4 verbose run-script [ 'preapp-package', 'app-package', 'postapp-package' ]
5 info lifecycle insomnia@1.0.0~preapp-package: insomnia@1.0.0
6 info lifecycle insomnia@1.0.0~app-package: insomnia@1.0.0
7 verbose lifecycle insomnia@1.0.0~app-package: unsafe-perm in lifecycle true
8 verbose lifecycle insomnia@1.0.0~app-package: PATH: REDACTED
9 verbose lifecycle insomnia@1.0.0~app-package: CWD: /home/leo/.cache/pikaur/build/insomnia/src/insomnia-core-2020.4.2
10 silly lifecycle insomnia@1.0.0~app-package: Args: [ '-c', 'npm run package --prefix packages/insomnia-app' ]
11 silly lifecycle insomnia@1.0.0~app-package: Returned: code: 1  signal: null
12 info lifecycle insomnia@1.0.0~app-package: Failed to exec app-package script
13 verbose stack Error: insomnia@1.0.0 app-package: `npm run package --prefix packages/insomnia-app`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (node:events:327:20)
13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (node:events:327:20)
13 verbose stack     at maybeClose (node:internal/child_process:1048:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:288:5)
14 verbose pkgid insomnia@1.0.0
15 verbose cwd /home/leo/.cache/pikaur/build/insomnia/src/insomnia-core-2020.4.2
16 verbose Linux 5.9.1-arch1-1
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "app-package"
18 verbose node v15.0.1
19 verbose npm  v6.14.8
20 error code ELIFECYCLE
21 error errno 1
22 error insomnia@1.0.0 app-package: `npm run package --prefix packages/insomnia-app`
22 error Exit status 1
23 error Failed at the insomnia@1.0.0 app-package script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

whynothugo commented on 2020-10-30 15:25 (UTC)

I'm getting an error building:

[package] Removing existing directories
[package] Packaging app
  • electron-builder  version=22.7.0 os=5.9.1-arch1-1
  • writing effective config  file=dist/com.insomnia.app/builder-effective-config.yaml
  ⨯ node_modules.Dependency.Dependencies: ReadMapCB: expect { or n, but found [, error found in #10 byte of ...|ncies" : [],
    "main|..., bigger context ...|/garycourt/JSV.git"
        }
    ],
    "dependencies" : [],
    "main" : "lib/jsv.js",
    "keywords" : ["json"|...
Error reading package.json: /home/hugo/.cache/yay/aurdata/insomnia/src/insomnia-core-2020.4.2/packages/insomnia-app/build/com.insomnia.app/node_modules/JSV/package.json
[package] ERROR: ExecError: /home/hugo/.cache/yay/aurdata/insomnia/src/insomnia-core-2020.4.2/packages/insomnia-app/node_modules/app-builder-bin/linux/x64/app-builder exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
    at ChildProcess.<anonymous> (/home/hugo/.cache/yay/aurdata/insomnia/src/insomnia-core-2020.4.2/packages/insomnia-app/node_modules/builder-util/src/util.ts:243:14)
    at Object.onceWrapper (node:events:434:26)
    at ChildProcess.emit (node:events:327:20)
    at maybeClose (node:internal/child_process:1048:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:288:5) {
  exitCode: 1,
  alreadyLogged: false,
  code: 'ERR_ELECTRON_BUILDER_CANNOT_EXECUTE'
}
npm ERR! code 1
npm ERR! path /home/hugo/.cache/yay/aurdata/insomnia/src/insomnia-core-2020.4.2/packages/insomnia-app
npm ERR! command failed
npm ERR! command sh -c node ./scripts/package.js

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/hugo/.npm/_logs/2020-10-30T15_24_43_147Z-debug.log
npm ERR! code 1
npm ERR! path /home/hugo/.cache/yay/aurdata/insomnia/src/insomnia-core-2020.4.2
npm ERR! command failed
npm ERR! command sh -c npm run package --prefix packages/insomnia-app

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/hugo/.npm/_logs/2020-10-30T15_24_43_171Z-debug.log

Any hints?

Kniyl commented on 2020-10-29 09:33 (UTC)

I got an error during the build:

⨯ Get "https://github.com/electron/electron/releases/download/v10.1.5/electron-v10.1.5-linux-x64.zip": dial tcp: lookup github.com on [::1]:53: read udp [::1]:52111->[::1]:53: read: connection refused

Is there something I can do on my end to fix it?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »