I haven't dabbled with Deno at all so far but I'm curious as to how people would tackle the missing script-section of the package.json.
For example I have a script:
"scripts": {
"coverage": "test script here",
"postcoverage": "do stuff after coverage is done",
Like you described we probably could setup some .sh or other centralized collection of scripts but ... aren't we just rebuilding the package.json at this point?
Without any of those you probably end up noting all your possible scripts somewhere in your readme so other devs know what to execute? Sounds iffy. Am I missing the obvious solution to this problem?
Also, how would a typical CI like GitHub actions work out? Let's say we have a GitHub action running whenever someone wants to merge into our master-branch. What does the github action execute? The .sh? I'm really open for new things but I just don't see any gain from this :|
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I haven't dabbled with Deno at all so far but I'm curious as to how people would tackle the missing script-section of the package.json.
For example I have a script:
Like you described we probably could setup some
.shor other centralized collection of scripts but ... aren't we just rebuilding the package.json at this point?Without any of those you probably end up noting all your possible scripts somewhere in your readme so other devs know what to execute? Sounds iffy. Am I missing the obvious solution to this problem?
Also, how would a typical CI like GitHub actions work out? Let's say we have a GitHub action running whenever someone wants to merge into our master-branch. What does the github action execute? The
.sh? I'm really open for new things but I just don't see any gain from this :|