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
Repository infrastructure setup #1
Conversation
cc/ @jeffersonking - you don't seem to be added as a contributor to the repo yet. |
@scalvert Re yarn vs npm, it sounds like |
@jeffersonking correct. The current plugin operates on yarn workspaces, and hasn't been tested with npm. That said, we own that plugin and can update/adjust it to work with both. |
@scalvert If all else is equal, the path with one less installation wins? So |
Yep, we can certainly explore either making that plugin work for npm, or make a similar plugin for npm. |
Looking at our plugin, I think it will work out-of-the-box, as it's not doing anything yarn specific. It likely could use a rename though... |
OK I've updated to use |
@scalvert Thanks! Not familiar with I think the there's still the big question of if the |
Ya I think the question of 'what else goes here' is for sure up for debate, but I can imagine the following:
Happy to defer these discussions until they present themselves later. |
@jeffersonking |
Wahoo! Every GitHub open source journey starts with a single merge! |
This PR adds initial repository setup, including
volta
to manage tool dependenciessarif-builder
packageAll infrastructure choices and naming conventions are open to feedback and changes.