This CLI application is made to convert Atom.io Archived Repository package data.

Intended that this data was originally archived via AtomPackagesArchive and will then be deployed to the new atom-community-server-backend-JS.

It is REQUIRED that you have the packages saved file by file, within the ./data directory, at the root of this project. Additionally it is REQUIRED to create a src/config.js file, look at src/config.exmaple.js file for reference. It will need to contain your GitHub username, and a PAT token for your account. This PAT token allows extended rate limiting, but USE AT YOUR OWN RISK it is possible for you to hit a rate limit during this process. Since every package hits the API twice, now the requests do wait some time between each one, make sure you understand the risks before using this.

Additionally more work has gone into preventing hitting a rate limit. With every request waiting 1.5 seconds between to where if each request takes a second that limit will never be hit. Otherwise the API will check every second request for how close the limit is to being reached. And if only 20 requests remain on your account, will stop, and pause until the moment the rate limit should be lifted.

If you have done that, run node . in the root of this project, and after some time you will see a ./dest/package_pointer.json and ./dest/packages/*.json files created.

The package_pointer contains the package_pointer that should be used on the new package, while the packages folder will contain the properly created and formatted packages for every single package.

Once the script finishes running you will likely see several Failed to Write:..... this is indicated a package that was unable to be written. This could be because of an error, or more likely the package is no longer allowed to be used within the new API server backend.

It will list a reason for this happening along with the error message.