Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notes #1

Open
natew opened this issue Feb 6, 2017 · 3 comments
Open

Notes #1

natew opened this issue Feb 6, 2017 · 3 comments

Comments

@natew
Copy link
Contributor

natew commented Feb 6, 2017

Lets make this a bit more focused to start. There are two high level directions, lets do the second:

  • Make managing lots of github repos easier
  • Make managing lots of small node packages easier

Goal is to be able to go from 0 to published package easy, and make ongoing maintenance easy. It's basically lerna sans mono-repo, maybe even more opinionated.

Goals for v1:

  1. Track directories
  2. Exec commands easily in all directories
  3. Share scripts between all repos easily (and have a default set that uses babel + presets-steelbrain)
  4. Be really good at linking stuff together thats tracked by it (lerna-style)

Bonus points:

  • See nice status of all repos
  • Publishing helpers
@natew
Copy link
Contributor Author

natew commented Feb 6, 2017

Problem: you need a way to share scripts, but these scripts should be tied to the version of the package so others can clone/edit stuff.

Idea:

  • have a key repoScripts automatically managed in package.json that points to commit SHA for those scripts: natew/reposcripts:a4d67ojs21
  • set npm run bootstrap to do npm install repoman && repoman bootstrap which then grabs the package.json and grabs the right reposcripts down
  • ... complexity unfolds....

@natew
Copy link
Contributor Author

natew commented Feb 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant