fetch() is a notable web feature missing from Node.js core
1,940 karma · joined September 20, 2016
[ my public key: https://keybase.io/styfle; my proof: https://keybase.io/styfle/sigs/k5Jx2P3fJ9JOZsHyU2TLChLetDsvmL2mHK7wJMj-nKk ]
Same with favicons, although you can specify an arbitrary path to most favicons using index.html
And sadly, you can't post emoji on hackernews comments :(
But the premise still stands, just needs more feature checkboxes :)
If I were building a static website in 2020, I would expect my provider to not only host the static files, but build from source when I `git push`. That narrows down the list to 5 so I would put those at the top.
Second, I would expect the products that don't come with static hosting out of the box to be at the bottom of the list.
For example, number 4 says "Heroku is free for non-commercial apps. It doesn’t offer hosting for static websites out-of-the-box but need some hacky tricks".
Disclaimer: I work for Vercel, one of the static hosts in this list :)
You looked at the size and determined that it might not be worth bringing on a small dependency when you can implement it yourself (or rather use String.prototype.padStart).
It’s not just size alone but size of transitive dependencies.
Both examples you gave don’t have any dependencies (the publish size matches the install size).
Take a look at some popular dependencies like request or jest and notice the number of transitive dependencies.
One such metric I found to be missing for npm dependencies was the install size, which is why I created https://packagephobia.com
We need more tools to help make this decision because its easy to add a new dependency but its often hard to remove a dependency.
It’s exciting to see this game is still worked on, I’ll have to dust off the old PC and try it out again!
I noticed there is a version for iOS—will iOS also get the update?
Why does Rust destructuring require the struct name? The example uses:
let Person { name, city } = person;
Is this because destructuring syntax is trying to be compatible with the pattern matching syntax?
cli add user1 -passWord
cli add user2 passw*
etc
https://vercel.com/docs/v2/serverless-functions/edge-caching
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Ca...
The blog post mentions the 3 APIs that make this possible:
- getStaticProps (Static Generation): Fetch data at build-time.
- getStaticPaths (Static Generation): Specify dynamic routes to prerender based on data.
- getServerSideProps (Server-Side Rendering): Fetch data on each request.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
1. This doesn’t bundle
2. This doesn’t support source maps
In Chrome (and probably other browsers), you can use CMD+Up to jump to the top and CMD+Down to jump to the bottom.
In this case, members of the TS team were actually championing these ES proposals :)
const enum Directions { Up, Down, Left, Right }
console.log(Directions.Left)
// emits js file with console.log(2)
The added benefit to becoming proficient with default configuration is that it is really easy to upgrade to a new computer and start from scratch.
And of course with vim, the benefit is the ubiquity when using ssh or docker or VMs which typically use the defaults.
There is a demo using Notion as the “backend” which is kind of like Google Docs. I could see this being a great solution for less technical authors who only want to deal with content.
In the end, it’s like a static site but you don’t wait for a build step.