pronouns | she/her |
main project | https://mermaid.industries |
on bsky | https://bsky.app/profile/dryad.technology |
avatar by | Dana |
pronouns | she/her |
main project | https://mermaid.industries |
on bsky | https://bsky.app/profile/dryad.technology |
avatar by | Dana |
absfbdsf no i screwed up. the problem is that astro heavily promotes use of typescript but its interface and tooling consider "your code has typescript errors" to be an extremely low priority thing to report
EDIT: Wait why does the sample code have typescript errors
Consulting the *other* sample code, for next.js, I think the problem might be
1. The sample code is wrong; it's creating promises that it doesn't await on
2. I think it might actually be the case this code is required to go into the server code, and I put it in the client code. This is awkward to test because Astro seems to require client and server code to go in different filetypes.
I wonder if I should have been using next.js to start with. I avoided that because I want Preact not React.
Alright after a few days and stitching together hello world code from the various Astro guides and tutorials I now have a site with a "login" button that per https://authjs.dev/getting-started/authentication/oauth is supposed to kick off the login oauth flow for mastodon.social. When I click "login" nothing happens. No error message appears in the js console nor in the window for the dev server. I guess I don't know what I expected to happen but probably not nothing.
https://git.gay/mcc/ts-bug/commit/5c762846259f4313366dec54aa87bf8e8f9215ca
Hm.
Electronic girl