https://github.com/atom-community/papm

Performant Atom Package Manager
https://github.com/atom-community/papm

apm atom npm package-manager pnpm yarn

Last synced: about 2 months ago
JSON representation

Performant Atom Package Manager

• Host: GitHub
• URL: https://github.com/atom-community/papm
• Owner: atom-community
• License: mit
• Created: 2021-07-20T23:57:38.000Z (over 3 years ago)
• Default Branch: master
• Last Pushed: 2023-10-04T22:14:09.000Z (over 1 year ago)
• Last Synced: 2024-04-15T01:57:40.501Z (9 months ago)
• Topics: apm, atom, npm, package-manager, pnpm, yarn
• Language: TypeScript
• Homepage:
• Size: 832 KB
• Stars: 8
• Watchers: 4
• Forks: 1
• Open Issues: 9
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

        
# papm

Performant Atom Package Manager

![Github Actions](https://github.com/atom-community/papm/workflows/CI/badge.svg)

[![Dependency Status](https://david-dm.org/atom-community/papm.svg)](https://david-dm.org/atom-community/papm)

# Roadmap

## Implementation Requirements (Future Features)

- `papm` shall use `pnpm`

- `papm` shall not use GitHub tags for publishing (See [this](https://github.com/atom/apm/issues/919) for the background)

- `papm` shall either publish the atom packages to a `npm` registry, or use GitHub packages

- `papm` shall be able to install the packages that are published on the old registry (backward compatibility)

- `papm` operations shall not block the UI

- `papm` shall handle failed installations, bad connections, etc.

## Strategy

The strategy I suggest is to:

- [x] decaffeinate each file

- [x] 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