This post is my 2nd write-down inspired by "Purescript by Example",
the book by Phil Freeman, the author of purescript.
Now about chapter 2, where I install Purescript and touch the tools
for the first time. I am gonna use yarn instead of npm,
let's see how that goes :).
browser field in npm's package.json
browser field in npm's package.json
Nothing to add to this post
JSON with CoffeeScript flavor
In order to keep all your meta data of your project in one place and only create files that actually just copy those data you can use projectz where you maintain data like title, description, author(s), badges, ... in one CSON file and with a special markup you can update fill in the templates files like README, package.json, ...
I am gladly using codeberg (as github alternative)
for as many projects as I can, really support their mission.
"Independent and powered by your donations and contributions".
I struggled a little bit to figure out the URL that works
for a package
that is not on npm yet, but exists just as a codeberg repo.
Continue reading →
Run npm install <package>@latest to update to the latest version of a package,
no matter the minor, major version, it always goes to the latest.