Package Details: atom-community-git 1.63.0_dev.r39017.g0f7c5c1-1

Git Clone URL: https://aur.archlinux.org/atom-community-git.git (read-only, click to copy)
Package Base: atom-community-git
Description: A hackable text editor for the 21st century, built on Electron, and based on everything we love about our favorite editors.
Upstream URL: https://github.com/atom-community/atom
Conflicts: apm, atom
Submitter: dhummel
Maintainer: None
Last Packager: dhummel
Votes: 2
Popularity: 0.000014
First Submitted: 2022-07-11 03:52 (UTC)
Last Updated: 2023-10-29 18:53 (UTC)

Latest Comments

« First ‹ Previous 1 2

moe_narrow commented on 2022-10-25 14:20 (UTC)

Not working to install with yay

apm  2.6.5-atomic.1.0
npm  6.14.17
node 12.18.3 x64
atom unknown
python 3.10.8
git 2.38.1
Installing modules ✗
> atom@1.63.0-dev preinstall /home/user/.cache/yay/atom-community-git/src/atom
> node -e 'process.exit(0)'


npm ERR! code E500
npm ERR! 500 Internal Server Error - GET https://www.atom.io/api/packages/language-gfm/versions/0.90.8/tarball

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.atom/.apm/_logs/2022-10-25T14_11_34_057Z-debug.log
Error: Command failed: /home/user/.cache/yay/atom-community-git/src/atom/apm/node_modules/atom-package-manager/bin/apm install
    at checkExecSyncError (node:child_process:828:11)
    at Object.execFileSync (node:child_process:863:15)
    at module.exports (/home/user/.cache/yay/atom-community-git/src/atom/script/lib/run-apm-install.js:12:16)
    at bootstrap (/home/user/.cache/yay/atom-community-git/src/atom/script/bootstrap.js:56:3)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
==> ERROR: A failure occurred in prepare().
    Aborting...
 -> error making: atom-community-git

kanmeiban commented on 2022-10-13 12:15 (UTC)

I get the following error when I try to build it with sudo pamac install:

==> Starting prepare()...
/var/cache/private/pamac/atom-community-git/src/atom /var/cache/private/pamac/atom-community-git/src
node:internal/validators:120
    throw new ERR_INVALID_ARG_TYPE(name, 'string', value);
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
    at new NodeError (node:internal/errors:372:5)
    at validateString (node:internal/validators:120:11)
    at Object.join (node:path:1172:7)
    at Object.<anonymous> (/var/cache/private/pamac/atom-community-git/src/atom/script/config.js:21:33)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18) {
  code: 'ERR_INVALID_ARG_TYPE'
}

alfrednewman commented on 2022-09-28 01:49 (UTC) (edited on 2022-09-28 01:59 (UTC) by alfrednewman)

It gets stuck on "Installing Modules" for a long time, but it's still doing something and will eventually install. Compiles fine and works well for me! Still keeps all the packages I have installed before like the file icon pack. Thanks for maintaining the AUR package, this works great

dhummel commented on 2022-08-24 22:07 (UTC) (edited on 2022-09-10 20:18 (UTC) by dhummel)

Yeah, there are still some minor issues with this PKGBUILD, but if you do get it to build, it at least works for basic editing.

  1. If you missed the sudo prompt, you can just run pacman -U ~/.cache/yay/... on the resulting package.
  2. This doesn't currently use the script you might have become familiar with if you were previously using the atom package.
  3. I'm not sure what to do about this at the moment. Re-installing the modules does seem to resolve at least some of the error messages for me.

Please feel free to post some fixes if you have any ideas. Thanks for the comment!

AlexWayfer commented on 2022-08-10 14:17 (UTC)

Some notes: 1. It doesn't install when you skipped a sudo requests, you have to do a new clean install (I'm using yay). 2. It has output and doesn't work in foreground as expected. 3. It has a lot of errors from extensions about /opt directory.

« First ‹ Previous 1 2