963 karma · joined April 30, 2016
Socials: - bsky.app/profile/precioso.design - github.com/cprecioso - linkedin.com/in/cprecioso
---
[ my public key: https://keybase.io/cprecioso; my proof: https://keybase.io/cprecioso/sigs/1X7I415iPxyBFFOSmQxGPcv4TWbhRi-3AHEjw2gU-Zw ]
I'm linking my keytrace.dev: did:plc:h22ajfwlv7pvlhxqzi3dsiaj
IANAL, but it seems you can only use the library if you have an active account, and you can still modify the code except billing and analytics. The it links to the TOS ( https://www.mapbox.com/legal/tos ).
`npx`’s specific use case, though, is specifically to run scripts that you haven’t installed - else you’d use `yarn/npm run whatever`.
For example, in English the "o" in "woman" and "women" sounds different, with exactly the same syllabic structure. However in Spanish, every time you write the "o" it is pronounced the same as every other "o". In some accents/dialects some letters will have slightly different pronunciations or intonations (e.g. c turns into s, or s at the end of a word will turn silent), but within that accent, most sounds will remain stably linked to a letter.
EDIT: Of course, I am not a linguist and I'm sure every word of my example can be debunked a million ways; but this is the experience of the language for a native Spain Spanish speaker.
On the other hand, in Spain we’re famous for “cecear”, that is to pronounce “c” as the z in zombie; while in the rest of Latin America the pronounce it more like an s.
https://developer.spotify.com/documentation/web-api/referenc... https://developer.spotify.com/documentation/web-api/referenc... https://developer.spotify.com/documentation/web-api/referenc...
The website itself is made with Next.js, and data-fetching is done through the SWR library.
Spotify on desktop already has a "History" option, but it's only available on desktop, and only shows you songs you listened to in that desktop client. My page shows you the last 50 songs, regardless of client.
Hope you find it useful!
edit: BTW, it is all open-source! https://github.com/cprecioso/lastify
`next export` makes a folder of static resources (HTML, packages client JS code, CSS). It also forces every page (even dynamic ones) to compile down to HTML.
- `next dev` starts the dev server with unoptimized code and webpack hot-reload
- `next build` compiles all your code to be ready for production (optimizations enabled and not hot-reloading, pages that aren't dynamic server-side get turned into regular HTML, etc)
- `next start` serves that production-ready bundle, with a bare-bones (but production-ready) server
- `next export` forces every page to compile down to HTML and gives you a folder of static markup and js you can upload to any static host
So yeah, `next start` is indeed production-ready, and similar to what major websites already do. (Also there's no soft, hard, or default dependency between webpack and react, but the starter template uses it to make life easier for devs)
At times like this is when I most think of Svelte’s aspiration, to remove the framework and compile its uses to regular DOM calls. It just bothers me so much with their magic syntax.
PS: Maybe something similar could be made for React Hooks? If a component doesn’t use any hooks it’s marked as static and doesn’t need the framework or to be re-hydrated. If it uses any, we only need to create a discrete React root for that component and its children.
There are random spot checks of course, but I don't think this would work elsewhere, not with the high level of citizen trust that there is here. I'm sure they lose some money to people enticed by easier stealing, but the flow of people is so much faster that it's probably worth it many times over.
I know I might use it as a web designer to send interactive snapshots of how the website currently looks/works to the client; instead of using an ephemeral URL and a tunnelling/proxy service.
Google has developed Signed HTTP Exchanges https://developers.google.com/web/updates/2018/11/signed-exc... that can then be bundled https://web.dev/web-bundles/ .
Its main motivation is the rehosting of AMP pages while verifying that the cache hasn't tampered with them; but it could be extended to sign and bundle API calls for redistribution if needed.
https://developers.google.com/web/updates/2018/11/signed-exc...
It's part of a family of technologies developed by Google to rehost AMP pages without losing the origin.
Once you get the hang of it, and use tools like [clasp](https://github.com/google/clasp), you can create semi-complicated automated workflows; which I still find delightful.
For one of my jobs, I created a form, that either on submit or on demand, creates a PDF with the data based off a template made with Slides, and emails it to me and to the person who filled it.
The code is as concise as the API allows, that is, not much. But it's saved us the need to have a manual workflow, or setup a server just for this service.