atom/update-package-dependencies

Calls 'apm update' from the project's path.

Atom

Atom and all repositories under Atom will be archived on December 15, 2022. Learn more in our official announcement

Atom is a hackable text editor for the 21st century, built on Electron, and based on everything we love about our favorite editors. We designed it to be deeply customizable, but still approachable using the default configuration.

Visit atom.io to learn more or visit the Atom forum.

Follow @AtomEditor on Twitter for important announcements.

This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].

Documentation

If you want to read about using Atom or developing packages in Atom, the Atom Flight Manual is free and available online. You can find the source to the manual in atom/flight-manual.atom.io.

The API reference for developing packages is also documented on Atom.io.

Installing

Prerequisites

• Git

macOS

Download the latest Atom release.

Atom will automatically update when a new release is available.

Windows

Download the latest Atom installer. AtomSetup.exe is 32-bit. For 64-bit systems, download AtomSetup-x64.exe.

Atom will automatically update when a new release is available.

You can also download atom-windows.zip (32-bit) or atom-x64-windows.zip (64-bit) from the releases page. The .zip version will not automatically update.

Using Chocolatey? Run cinst Atom to install the latest version of Atom.

Linux

Atom is only available for 64-bit Linux systems.

Configure your distribution's package manager to install and update Atom by following the Linux installation instructions in the Flight Manual. You will also find instructions on how to install Atom's official Linux packages without using a package repository, though you will not get automatic updates after installing Atom this way.

Archive extraction

An archive is available for people who don't want to install atom as root.

This version enables you to install multiple Atom versions in parallel. It has been built on Ubuntu 64-bit, but should be compatible with other Linux distributions.

1. Install dependencies (on Ubuntu):

sudo apt install git libasound2 libcurl4 libgbm1 libgcrypt20 libgtk-3-0 libnotify4 libnss3 libglib2.0-bin xdg-utils libx11-xcb1 libxcb-dri3-0 libxss1 libxtst6 libxkbfile1

2. Download atom-amd64.tar.gz from the Atom releases page.
3. Run tar xf atom-amd64.tar.gz in the directory where you want to extract the Atom folder.
4. Launch Atom using the installed atom command from the newly extracted directory.

The Linux version does not currently automatically update so you will need to repeat these steps to upgrade to future releases.

Building

• Linux
• macOS
• Windows

Discussion

• Discuss Atom on GitHub Discussions

License

MIT

When using the Atom or other GitHub logos, be sure to follow the GitHub logo guidelines.

update-package-dependencies's Issues

running 'apm update' errors out

When trying to run apm update from command line, it errors. Checked the help documentation and it recommended running clean and install. clean worked, installed failed with the same error listed below.

The only package.json that exist are within individual package directories. Here's the error:

$ apm update
Installing modules ✗

npm ERR! install Couldn't read dependencies
npm ERR! package.json ENOENT, open '/Users/brint/package.json'
npm ERR! package.json This is most likely not a problem with npm itself.
npm ERR! package.json npm can't find a package.json file in your current directory.

npm ERR! System Darwin 12.5.0
npm ERR! command "/usr/local/Cellar/node/0.10.21/bin/node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/atom-package-manager/node_modules/npm/bin/npm-cli.js" "--userconfig" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/atom-package-manager/.apmrc" "install" "--target=0.11.10" "--arch=x64"
npm ERR! cwd /Users/brint
npm ERR! node -v v0.10.21
npm ERR! npm -v 1.3.18
npm ERR! path /Users/brint/package.json
npm ERR! code ENOPACKAGEJSON
npm ERR! errno 34
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/brint/npm-debug.log
npm ERR! not ok code 0

Here's the log:

$ cat npm-debug.log 
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/Cellar/node/0.10.21/bin/node',
1 verbose cli   '/Applications/Atom.app/Contents/Resources/app/apm/node_modules/atom-package-manager/node_modules/npm/bin/npm-cli.js',
1 verbose cli   '--userconfig',
1 verbose cli   '/Applications/Atom.app/Contents/Resources/app/apm/node_modules/atom-package-manager/.apmrc',
1 verbose cli   'install',
1 verbose cli   '--target=0.11.10',
1 verbose cli   '--arch=x64' ]
2 info using [email protected]
3 info using [email protected]
4 error install Couldn't read dependencies
5 error package.json ENOENT, open '/Users/brint/package.json'
5 error package.json This is most likely not a problem with npm itself.
5 error package.json npm can't find a package.json file in your current directory.
6 error System Darwin 12.5.0
7 error command "/usr/local/Cellar/node/0.10.21/bin/node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/atom-package-manager/node_modules/npm/bin/npm-cli.js" "--userconfig" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/atom-package-manager/.apmrc" "install" "--target=0.11.10" "--arch=x64"
8 error cwd /Users/brint
9 error node -v v0.10.21
10 error npm -v 1.3.18
11 error path /Users/brint/package.json
12 error code ENOPACKAGEJSON
13 error errno 34
14 verbose exit [ 34, true ]

Here are the places that package.json was found to exist:

~/.atom/.node-gyp/.atom/.apm/fizzy/0.7.0/package/package.json
~/.atom/.node-gyp/.atom/.apm/monokai/0.2.0/package/package.json
~/.atom/.node-gyp/.atom/.apm/sort-lines/0.2.0/package/package.json
~/.atom/.node-gyp/.atom/.apm/underscore/1.5.2/package/package.json
~/.atom/.node-gyp/.atom/.apm/underscore-plus/1.0.0/package/package.json
~/.atom/packages/editor-stats/node_modules/d3-browserify/package.json
~/.atom/packages/editor-stats/node_modules/underscore-plus/node_modules/underscore/package.json
~/.atom/packages/editor-stats/node_modules/underscore-plus/package.json
~/.atom/packages/editor-stats/package.json
~/.atom/packages/fizzy/package.json
~/.atom/packages/monokai/package.json
~/.atom/packages/sort-lines/package.json

Error message panel can't be discarded once displayed

I just encountered it as I was trying the command (I mostly use apm update these days). I got an error during the update, and got this message displayed:

The first problem is that once this message appears there's no way to make it disappears (except yb removing it from the DOM using the devtools).

The second problem is that the message is probably a bit light, having some kind of information about the source of the issue would be better (to know if it's the command that failed, a network error, etc.)

Disabled packages

Description

1. Disabled packages should not be counted ((N) Updates message at the bottom-right corner)

2. Notification should not tell user to restart Atom to apply changes to disabled packages (or, notification shouldn't show up at all) because it makes no sense and just annoying