updated 2023-07-14
Version 2304? (Build 16.0.16327.20264)
| # npm publish with goodies | |
| # prerequisites: | |
| # `npm install -g trash conventional-recommended-bump conventional-changelog conventional-github-releaser conventional-commits-detector json` | |
| # `np` with optional argument `patch`/`minor`/`major`/`<version>` | |
| # defaults to conventional-recommended-bump | |
| # and optional argument preset `angular`/ `jquery` ... | |
| # defaults to conventional-commits-detector | |
| np() { | |
| travis status --no-interactive && | |
| trash node_modules &>/dev/null; |
| # Hello, and welcome to makefile basics. | |
| # | |
| # You will learn why `make` is so great, and why, despite its "weird" syntax, | |
| # it is actually a highly expressive, efficient, and powerful way to build | |
| # programs. | |
| # | |
| # Once you're done here, go to | |
| # http://www.gnu.org/software/make/manual/make.html | |
| # to learn SOOOO much more. |
Since this is on Hacker News and reddit...
_t in my types. I spend a lot of time at a level where I can do that; "reserved for system libraries? I am the system libraries".char *s.type * name, however, is entirely intentional.At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.