Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Generic Node.js Action #9
I use Yarn instead of NPM for all my projects. When I run my linter, I do it by running
My above command is using the
Is the intended design to always have one command per action? Would you expect me to create a
I think I might understand now. It looks like
Does that seem like the right way to go?
Happy New Year! I'm brand new to GitHub Actions and alas I'm still waiting for someone to click the "give John Reilly access to the beta" button. No doubt that's in the post. I'm planning to use GitHub actions to automate the publishing of a project I work on called ts-loader to npm.
All of which is background. The reason I'm writing this comment is you're at least a month ahead of me on this GitHub Actions thing and I'm hoping I can pick your brains. If you've no time to answer then no sweat; but to quote my father "if you don't ask, you don't get"
Should these questions seem a bit obvious then please forgive me; I'm no expert on docker and I'm certainly no expert on GitHub Actions.
Like you, ts-loader very much requires yarn. To that end I've read a whole bunch of
The above is hand crafted since I don't yet have access to the beta. There are likely some wrong bits but hopefully you get the gist; we install, build and test using yarn and then publish with npm.
All of which should hopefully work based upon what you've said in your first comment. Since yarn is included in
It kind of depends on what you want to accomplish. Smaller images will boot faster but that means you'll need to maintain more images to accomplish your goals. We've focused on creating images around single binaries but feel free to create images that include more than one.
It looks right to me. The biggest suggestion I would make is to use a specific version ie
If your intent is to run an action with Node I'd actually say that the npm action doesn't offer you anything specifically and you should feel free to use existing docker images.
Suprisingly, the answer is actually yes. You can use whatever docker container or action you would like for each step of the process.
Wow! That's amazing
@mcolyer would you be able to get myself / TypeStrong access to the beta? I've applied on behalf of both myself and TypeStrong but not heard anything yet... (ts-loader lives under TypeStrong: https://github.com/TypeStrong/ts-loader )
Thanks for the help - I've blogged about my learnings so far: https://blog.johnnyreilly.com/2019/01/github-actions-and-yarn.html