|
That hosting is transpiling down to require() based imports separate for each module and thus there is no shared state. Practice using the  devtools, add a break point in the Render API and step through and watch the global state .
|
#
¿
Nov 4, 2023 01:43
|
|
|
|
| # ¿ May 15, 2024 08:37 |
|
|
It’s a bit sad devs would rather drop a platform rather than address the defects with the tooling that blocks integration. Normally in webdev land that ignites creation of a dozen new tools.
|
|
#
¿
Jan 18, 2024 21:57
|
|
|
lol, use Luxon DateTime for anything more than fetching the current time. REF: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date quote:Note: While the time value at the heart of a Date object is UTC, the basic methods to fetch the date and time or its components all work in the local (i.e. host system) time zone and offset. The long form date is in the local timezone, the short form date is in UTC. NodeJS CLI is good for debugging this. code:
|
|
#
¿
Mar 19, 2024 18:45
|
|
|
Obfuscation posted:Does anyone know why Temporal is still not ready? Blame Microsoft for wanting a 1601 epoch and 100ns units? It has to be something esoteric, probably more related to the multitude of complex calendaring schemes. There are two polyfills though: https://github.com/js-temporal/temporal-polyfill#readme https://github.com/fullcalendar/temporal-polyfill#readme I was impressed a lot of nice stuff has been hitting V8 recently: https://v8.dev/blog/holiday-season-2023#:~:text=New%20JavaScript%20features MrMoo fucked around with this message at 20:57 on Mar 19, 2024 |
|
#
¿
Mar 19, 2024 20:52
|
|