Performant Atom Package Manager
papm
shall usepnpm
papm
shall not use GitHub tags for publishing (See this for the background)papm
shall either publish the atom packages to anpm
registry, or use GitHub packagespapm
shall be able to install the packages that are published on the old registry (backward compatibility)papm
operations shall not block the UIpapm
shall handle failed installations, bad connections, etc.
The strategy I suggest is to:
- decaffeinate each file
- improve build process
- replace the old dependencies of the resulting code with modern replacements
- replace npm things with pnpm
- In the end, we can think about publishing on the
npm
registry or using Github packages