home.social

#js β€” Public Fediverse posts

Live and recent posts from across the Fediverse tagged #js, aggregated by home.social.

  1. π•‚πšžπš‹πš’πš”β„™πš’πš‘πšŽπš• @[email protected] Β·

    CSS vs. JavaScript:
    Exploring the performance implications of different animation strategies

    One of the most common questions around animation performance is whether JS-based animations are slower than CSS-based ones. Should we always strive to use CSS transitions, or is it OK to use JavaScript animation libraries?

    πŸ˜‰ joshwcomeau.com/animation/css-

    #css #javascript #webdesign #web #js #performance #webdev #animation #slow #fast #design #faster #animation #anim

    #css #javascript #webdesign #web #js #performance
  2. π•‚πšžπš‹πš’πš”β„™πš’πš‘πšŽπš• @[email protected] Β·

    CSS vs. JavaScript:
    Exploring the performance implications of different animation strategies

    One of the most common questions around animation performance is whether JS-based animations are slower than CSS-based ones. Should we always strive to use CSS transitions, or is it OK to use JavaScript animation libraries?

    πŸ˜‰ joshwcomeau.com/animation/css-

    #css #javascript #webdesign #web #js #performance #webdev #animation #slow #fast #design #faster #animation #anim

    #css #javascript #webdesign #web #js #performance
  3. π•‚πšžπš‹πš’πš”β„™πš’πš‘πšŽπš• @[email protected] Β·

    CSS vs. JavaScript:
    Exploring the performance implications of different animation strategies

    One of the most common questions around animation performance is whether JS-based animations are slower than CSS-based ones. Should we always strive to use CSS transitions, or is it OK to use JavaScript animation libraries?

    πŸ˜‰ joshwcomeau.com/animation/css-

    #css #javascript #webdesign #web #js #performance #webdev #animation #slow #fast #design #faster #animation #anim

    #css #javascript #webdesign #web #js #performance
  4. π•‚πšžπš‹πš’πš”β„™πš’πš‘πšŽπš• @[email protected] Β·

    CSS vs. JavaScript:
    Exploring the performance implications of different animation strategies

    One of the most common questions around animation performance is whether JS-based animations are slower than CSS-based ones. Should we always strive to use CSS transitions, or is it OK to use JavaScript animation libraries?

    πŸ˜‰ joshwcomeau.com/animation/css-

    #css #javascript #webdesign #web #js #performance #webdev #animation #slow #fast #design #faster #animation #anim

    #anim #faster #design #fast #slow #animation
  5. π•‚πšžπš‹πš’πš”β„™πš’πš‘πšŽπš• @[email protected] Β·

    CSS vs. JavaScript:
    Exploring the performance implications of different animation strategies

    One of the most common questions around animation performance is whether JS-based animations are slower than CSS-based ones. Should we always strive to use CSS transitions, or is it OK to use JavaScript animation libraries?

    πŸ˜‰ joshwcomeau.com/animation/css-

    #css #javascript #webdesign #web #js #performance #webdev #animation #slow #fast #design #faster #animation #anim

    #css #javascript #webdesign #web #js #performance
  6. adb @[email protected] Β·

    I just want to say FUCK YOU NPMJS.COM for making me having to create a new access token every 90 days maximum, and for offering a shitty 2FA without TOTP option

    #npm #developer #webdeveloper #node #npmpackage #javascript #nodejs #node #OpenSource #FreeSoftware #js #typescrypt #web #programmer #npmjs

    #npm #developer #webdeveloper #node #npmpackage #javascript
  7. adb @[email protected] Β·

    I just want to say FUCK YOU NPMJS.COM for making me having to create a new access token every 90 days maximum, and for offering a shitty 2FA without TOTP option

    #npm #developer #webdeveloper #node #npmpackage #javascript #nodejs #node #OpenSource #FreeSoftware #js #typescrypt #web #programmer #npmjs

    #npm #developer #webdeveloper #node #npmpackage #javascript
  8. adb @[email protected] Β·

    I just want to say FUCK YOU NPMJS.COM for making me having to create a new access token every 90 days maximum, and for offering a shitty 2FA without TOTP option

    #npm #developer #webdeveloper #node #npmpackage #javascript #nodejs #node #OpenSource #FreeSoftware #js #typescrypt #web #programmer #npmjs

    #npm #developer #webdeveloper #node #npmpackage #javascript
  9. adb @[email protected] Β·

    I just want to say FUCK YOU NPMJS.COM for making me having to create a new access token every 90 days maximum, and for offering a shitty 2FA without TOTP option

    #npm #developer #webdeveloper #node #npmpackage #javascript #nodejs #node #OpenSource #FreeSoftware #js #typescrypt #web #programmer #npmjs

    #npmjs #programmer #web #typescrypt #js #freesoftware
  10. adb @[email protected] Β·

    I just want to say FUCK YOU NPMJS.COM for making me having to create a new access token every 90 days maximum, and for offering a shitty 2FA without TOTP option

    #npm #developer #webdeveloper #node #npmpackage #javascript #nodejs #node #OpenSource #FreeSoftware #js #typescrypt #web #programmer #npmjs

    #npm #developer #webdeveloper #node #npmpackage #javascript
  11. Ido Green @[email protected] Β·

    Unlock WhatsApp Data with Local Analytics Dashboard

    Most people think of WhatsApp as β€œjust messaging.”

    But after years of conversations, support threads, customer discussions, team coordination, and random life moments… it quietly becomes one of the richest personal datasets you own.

    So I built wacrawl-ui β€” a local analytics dashboard for WhatsApp archives generated by wacrawl.

    The idea is simple:

    • Your data stays local
    • No cloud sync
    • No browser extension
    • No scraping APIs
    • No β€œAI magic” uploading your chats somewhere

    Just a fast local dashboard on top of SQLite.

    What’s inside:

    • Full-text search (FTS5) – It’s working quite fast. Even on ~100k messages.
    • Messaging activity analytics
    • Contact insights
    • Media browsing
    • Response-time patterns
    • Word clouds
    • Group activity stats
    • Read-only local API
    • React + Vite frontend
    • Express backend
    • Zero external dependencies once running – You only need to make sure you run β€˜wacrawl syncβ€˜ before.

    A few things I found interesting while building it:

    1. SQLite is still absurdly powerful
      People underestimate what you can do locally with FTS indexes and good schema design.
    2. β€œLocal-first” UX matters more than ever
      We’ve normalized uploading deeply personal data to random SaaS products. We should challenge that assumption.
    3. Personal analytics is an untapped category
      Not surveillance. Not ad targeting.
      Tools that help you understand your own data.
    4. Read-only architectures reduce risk dramatically
      The app intentionally avoids mutation flows. That constraint simplified security and reliability decisions across the stack.

    The whole thing runs with one line:

     npx wacrawl-dashboard@latest

    No complicated setup.

    Still early, but I think there’s a broader shift happening toward:

    • local AI – Ollama for the win.
    • local analytics – secure, private and handy.
    • local search – that works fast.
    • user-owned datasets – It’s not for everyone, but it’s useful.

    Well, that future feels healthier.

    Feel free to check the repo: github.com/greenido/wacrawl-ui and contribute.

    Be strong.

    Rate this:

    #dashboard #Developer #JS #LLM #localAi #whatsapp
    #dashboard #developer #js #llm #localai #whatsapp
  12. Ido Green @[email protected] Β·

    Unlock WhatsApp Data with Local Analytics Dashboard

    Most people think of WhatsApp as β€œjust messaging.”

    But after years of conversations, support threads, customer discussions, team coordination, and random life moments… it quietly becomes one of the richest personal datasets you own.

    So I built wacrawl-ui β€” a local analytics dashboard for WhatsApp archives generated by wacrawl.

    The idea is simple:

    • Your data stays local
    • No cloud sync
    • No browser extension
    • No scraping APIs
    • No β€œAI magic” uploading your chats somewhere

    Just a fast local dashboard on top of SQLite.

    What’s inside:

    • Full-text search (FTS5) – It’s working quite fast. Even on ~100k messages.
    • Messaging activity analytics
    • Contact insights
    • Media browsing
    • Response-time patterns
    • Word clouds
    • Group activity stats
    • Read-only local API
    • React + Vite frontend
    • Express backend
    • Zero external dependencies once running – You only need to make sure you run β€˜wacrawl syncβ€˜ before.

    A few things I found interesting while building it:

    1. SQLite is still absurdly powerful
      People underestimate what you can do locally with FTS indexes and good schema design.
    2. β€œLocal-first” UX matters more than ever
      We’ve normalized uploading deeply personal data to random SaaS products. We should challenge that assumption.
    3. Personal analytics is an untapped category
      Not surveillance. Not ad targeting.
      Tools that help you understand your own data.
    4. Read-only architectures reduce risk dramatically
      The app intentionally avoids mutation flows. That constraint simplified security and reliability decisions across the stack.

    The whole thing runs with one line:

     npx wacrawl-dashboard@latest

    No complicated setup.

    Still early, but I think there’s a broader shift happening toward:

    • local AI – Ollama for the win.
    • local analytics – secure, private and handy.
    • local search – that works fast.
    • user-owned datasets – It’s not for everyone, but it’s useful.

    Well, that future feels healthier.

    Feel free to check the repo: github.com/greenido/wacrawl-ui and contribute.

    Be strong.

    #dashboard #Developer #JS #LLM #localAi #whatsapp
    #dashboard #developer #js #llm #localai #whatsapp
  13. Ido Green @[email protected] Β·

    Unlock WhatsApp Data with Local Analytics Dashboard

    Most people think of WhatsApp as β€œjust messaging.”

    But after years of conversations, support threads, customer discussions, team coordination, and random life moments… it quietly becomes one of the richest personal datasets you own.

    So I built wacrawl-ui β€” a local analytics dashboard for WhatsApp archives generated by wacrawl.

    The idea is simple:

    • Your data stays local
    • No cloud sync
    • No browser extension
    • No scraping APIs
    • No β€œAI magic” uploading your chats somewhere

    Just a fast local dashboard on top of SQLite.

    What’s inside:

    • Full-text search (FTS5) – It’s working quite fast. Even on ~100k messages.
    • Messaging activity analytics
    • Contact insights
    • Media browsing
    • Response-time patterns
    • Word clouds
    • Group activity stats
    • Read-only local API
    • React + Vite frontend
    • Express backend
    • Zero external dependencies once running – You only need to make sure you run β€˜wacrawl syncβ€˜ before.

    A few things I found interesting while building it:

    1. SQLite is still absurdly powerful
      People underestimate what you can do locally with FTS indexes and good schema design.
    2. β€œLocal-first” UX matters more than ever
      We’ve normalized uploading deeply personal data to random SaaS products. We should challenge that assumption.
    3. Personal analytics is an untapped category
      Not surveillance. Not ad targeting.
      Tools that help you understand your own data.
    4. Read-only architectures reduce risk dramatically
      The app intentionally avoids mutation flows. That constraint simplified security and reliability decisions across the stack.

    The whole thing runs with one line:

     npx wacrawl-dashboard@latest

    No complicated setup.

    Still early, but I think there’s a broader shift happening toward:

    • local AI – Ollama for the win.
    • local analytics – secure, private and handy.
    • local search – that works fast.
    • user-owned datasets – It’s not for everyone, but it’s useful.

    Well, that future feels healthier.

    Feel free to check the repo: github.com/greenido/wacrawl-ui and contribute.

    Be strong.

    Rate this:

    #dashboard #Developer #JS #LLM #localAi #whatsapp
    #dashboard #developer #js #llm #localai #whatsapp
  14. Ido Green @[email protected] Β·

    Unlock WhatsApp Data with Local Analytics Dashboard

    Most people think of WhatsApp as β€œjust messaging.”

    But after years of conversations, support threads, customer discussions, team coordination, and random life moments… it quietly becomes one of the richest personal datasets you own.

    So I built wacrawl-ui β€” a local analytics dashboard for WhatsApp archives generated by wacrawl.

    The idea is simple:

    • Your data stays local
    • No cloud sync
    • No browser extension
    • No scraping APIs
    • No β€œAI magic” uploading your chats somewhere

    Just a fast local dashboard on top of SQLite.

    What’s inside:

    • Full-text search (FTS5) – It’s working quite fast. Even on ~100k messages.
    • Messaging activity analytics
    • Contact insights
    • Media browsing
    • Response-time patterns
    • Word clouds
    • Group activity stats
    • Read-only local API
    • React + Vite frontend
    • Express backend
    • Zero external dependencies once running – You only need to make sure you run β€˜wacrawl syncβ€˜ before.

    A few things I found interesting while building it:

    1. SQLite is still absurdly powerful
      People underestimate what you can do locally with FTS indexes and good schema design.
    2. β€œLocal-first” UX matters more than ever
      We’ve normalized uploading deeply personal data to random SaaS products. We should challenge that assumption.
    3. Personal analytics is an untapped category
      Not surveillance. Not ad targeting.
      Tools that help you understand your own data.
    4. Read-only architectures reduce risk dramatically
      The app intentionally avoids mutation flows. That constraint simplified security and reliability decisions across the stack.

    The whole thing runs with one line:

     npx wacrawl-dashboard@latest

    No complicated setup.

    Still early, but I think there’s a broader shift happening toward:

    • local AI – Ollama for the win.
    • local analytics – secure, private and handy.
    • local search – that works fast.
    • user-owned datasets – It’s not for everyone, but it’s useful.

    Well, that future feels healthier.

    Feel free to check the repo: github.com/greenido/wacrawl-ui and contribute.

    Be strong.

    Rate this:

    #dashboard #Developer #JS #LLM #localAi #whatsapp
    #whatsapp #localai #llm #js #developer #dashboard
  15. flo @[email protected] Β·
    Ich finde diese verschiedenen Spamschutz-Maßnahmen, um E-Mail-Adresse auf Internetseiten vor Crawlern zu "verstecken", spannend:
    https://spencermortensen.com/articles/email-obfuscation/

    Allerdings erfordern die alle, dass man selbst im HTML-Quelltext schreiben kann.

    Wenn ich nun ein CMS habe, in dem ich nicht das HTML, sondern ausschließlich Markdown schreiben kann, wie verhÀlt es sich da mit den vorgestellten Lâsungen, bzw. wie kânnen die in Markdown "umgeschrieben" werden?

    #Followerpower #WebDev #EMail #EMailVerschleierung #Spamschutz #HTML #CSS #JS #Markdown #SpencerMortensen
    #css #email #emailverschleierung #followerpower #html #js
  16. Patrick :neocat_flag_bi: @[email protected] Β·

    One Open-source Project Daily

    Build terminal dashboards using ascii/ansi art and javascript

    https://github.com/yaronn/blessed-contrib

    #1ospd #opensource #terminal #js #javascript

    #1ospd #opensource #terminal #js #javascript
  17. π•‚πšžπš‹πš’πš”β„™πš’πš‘πšŽπš• @[email protected] Β·

    Β«Hunderte bΓΆsartige npm-Pakete im AntV-Γ–kosystem entdeckt:
    Das Datenvisualisierungs-Γ–kosystem AntV war Ziel einer Mini-Shai-Hulud-Lieferkettenattacke mit Hunderten schΓ€dlicher npm-Pakete.Β»

    Schon wieder viele npm-Pakete. Liegt das an npm selber oder ist dies im allgemeinen ein Code-Struktur-Fehler? Betreffen tut es schlussendlich alle User dieser Software, auch wenn die es "nur" nutzen.

    πŸ§‘β€πŸ’» heise.de/news/Hunderte-boesart

    #npm #minishaihulud #itsicherheit #js #ts #javascript #typescript #webdev #antv

    #npm #minishaihulud #itsicherheit #js #ts #javascript
  18. π•‚πšžπš‹πš’πš”β„™πš’πš‘πšŽπš• @[email protected] Β·

    Β«Hunderte bΓΆsartige npm-Pakete im AntV-Γ–kosystem entdeckt:
    Das Datenvisualisierungs-Γ–kosystem AntV war Ziel einer Mini-Shai-Hulud-Lieferkettenattacke mit Hunderten schΓ€dlicher npm-Pakete.Β»

    Schon wieder viele npm-Pakete. Liegt das an npm selber oder ist dies im allgemeinen ein Code-Struktur-Fehler? Betreffen tut es schlussendlich alle User dieser Software, auch wenn die es "nur" nutzen.

    πŸ§‘β€πŸ’» heise.de/news/Hunderte-boesart

    #npm #minishaihulud #itsicherheit #js #ts #javascript #typescript #webdev #antv

    #npm #minishaihulud #itsicherheit #js #ts #javascript
  19. π•‚πšžπš‹πš’πš”β„™πš’πš‘πšŽπš• @[email protected] Β·

    Β«Hunderte bΓΆsartige npm-Pakete im AntV-Γ–kosystem entdeckt:
    Das Datenvisualisierungs-Γ–kosystem AntV war Ziel einer Mini-Shai-Hulud-Lieferkettenattacke mit Hunderten schΓ€dlicher npm-Pakete.Β»

    Schon wieder viele npm-Pakete. Liegt das an npm selber oder ist dies im allgemeinen ein Code-Struktur-Fehler? Betreffen tut es schlussendlich alle User dieser Software, auch wenn die es "nur" nutzen.

    πŸ§‘β€πŸ’» heise.de/news/Hunderte-boesart

    #npm #minishaihulud #itsicherheit #js #ts #javascript #typescript #webdev #antv

    #npm #minishaihulud #itsicherheit #js #ts #javascript
  20. π•‚πšžπš‹πš’πš”β„™πš’πš‘πšŽπš• @[email protected] Β·

    Β«Hunderte bΓΆsartige npm-Pakete im AntV-Γ–kosystem entdeckt:
    Das Datenvisualisierungs-Γ–kosystem AntV war Ziel einer Mini-Shai-Hulud-Lieferkettenattacke mit Hunderten schΓ€dlicher npm-Pakete.Β»

    Schon wieder viele npm-Pakete. Liegt das an npm selber oder ist dies im allgemeinen ein Code-Struktur-Fehler? Betreffen tut es schlussendlich alle User dieser Software, auch wenn die es "nur" nutzen.

    πŸ§‘β€πŸ’» heise.de/news/Hunderte-boesart

    #npm #minishaihulud #itsicherheit #js #ts #javascript #typescript #webdev #antv

    #antv #webdev #typescript #javascript #ts #js
  21. π•‚πšžπš‹πš’πš”β„™πš’πš‘πšŽπš• @[email protected] Β·

    Β«Hunderte bΓΆsartige npm-Pakete im AntV-Γ–kosystem entdeckt:
    Das Datenvisualisierungs-Γ–kosystem AntV war Ziel einer Mini-Shai-Hulud-Lieferkettenattacke mit Hunderten schΓ€dlicher npm-Pakete.Β»

    Schon wieder viele npm-Pakete. Liegt das an npm selber oder ist dies im allgemeinen ein Code-Struktur-Fehler? Betreffen tut es schlussendlich alle User dieser Software, auch wenn die es "nur" nutzen.

    πŸ§‘β€πŸ’» heise.de/news/Hunderte-boesart

    #npm #minishaihulud #itsicherheit #js #ts #javascript #typescript #webdev #antv

    #npm #minishaihulud #itsicherheit #js #ts #javascript
  22. Habr @[email protected] Β·

    Navigation API Ρ‚Π΅ΠΏΠ΅Ρ€ΡŒ доступСн Π² Baseline

    Navigation API прСдоставляСт Π²ΠΎΠ·ΠΌΠΎΠΆΠ½ΠΎΡΡ‚ΡŒ ΠΈΠ½ΠΈΡ†ΠΈΠΈΡ€ΠΎΠ²Π°Ρ‚ΡŒ (ΠΏΡ€ΠΎΠ³Ρ€Π°ΠΌΠΌΠ½ΠΎ Π·Π°ΠΏΡƒΡΠΊΠ°Ρ‚ΡŒ), ΠΏΠ΅Ρ€Π΅Ρ…Π²Π°Ρ‚Ρ‹Π²Π°Ρ‚ΡŒ ΠΈ ΡƒΠΏΡ€Π°Π²Π»ΡΡ‚ΡŒ Π½Π°Π²ΠΈΠ³Π°Ρ†ΠΈΠ΅ΠΉ Π² Π±Ρ€Π°ΡƒΠ·Π΅Ρ€Π΅. Он Ρ‚Π°ΠΊΠΆΠ΅ позволяСт ΠΈΡΡΠ»Π΅Π΄ΠΎΠ²Π°Ρ‚ΡŒ (traverse) сущности истории (history entries) прилоТСния. Π­Ρ‚ΠΎ ΡƒΠ»ΡƒΡ‡ΡˆΠ΅Π½Π½Ρ‹ΠΉ Π²Π°Ρ€ΠΈΠ°Π½Ρ‚ ΠΏΡ€Π΅Π΄Ρ‹Π΄ΡƒΡ‰ΠΈΡ… возмоТностСй Π²Π΅Π±-ΠΏΠ»Π°Ρ‚Ρ„ΠΎΡ€ΠΌΡ‹, связанных с Π½Π°Π²ΠΈΠ³Π°Ρ†ΠΈΠ΅ΠΉ, Ρ‚Π°ΠΊΠΈΡ… ΠΊΠ°ΠΊ History API ΠΈ window.location , ΠΊΠΎΡ‚ΠΎΡ€Ρ‹ΠΉ Ρ€Π΅ΡˆΠ°Π΅Ρ‚ ΠΈΡ… ΠΏΡ€ΠΎΠ±Π»Π΅ΠΌΡ‹ ΠΈ ΡΠΏΠ΅Ρ†ΠΈΠ°Π»ΡŒΠ½ΠΎ ΠΏΡ€Π΅Π΄Π½Π°Π·Π½Π°Ρ‡Π΅Π½ для одностраничных ΠΏΡ€ΠΈΠ»ΠΎΠΆΠ΅Π½ΠΈΠΉ (single-page applications, SPA).

    habr.com/ru/companies/timeweb/

    #javascript #js #web_api #webapi #navigation #history #навигация #история #timeweb_ΡΡ‚Π°Ρ‚ΡŒΠΈ #ti

    #ti #timeweb_ΡΡ‚Π°Ρ‚ΡŒΠΈ #история #навигация #history #navigation
  23. Habr @[email protected] Β·

    Navigation API Ρ‚Π΅ΠΏΠ΅Ρ€ΡŒ доступСн Π² Baseline

    Navigation API прСдоставляСт Π²ΠΎΠ·ΠΌΠΎΠΆΠ½ΠΎΡΡ‚ΡŒ ΠΈΠ½ΠΈΡ†ΠΈΠΈΡ€ΠΎΠ²Π°Ρ‚ΡŒ (ΠΏΡ€ΠΎΠ³Ρ€Π°ΠΌΠΌΠ½ΠΎ Π·Π°ΠΏΡƒΡΠΊΠ°Ρ‚ΡŒ), ΠΏΠ΅Ρ€Π΅Ρ…Π²Π°Ρ‚Ρ‹Π²Π°Ρ‚ΡŒ ΠΈ ΡƒΠΏΡ€Π°Π²Π»ΡΡ‚ΡŒ Π½Π°Π²ΠΈΠ³Π°Ρ†ΠΈΠ΅ΠΉ Π² Π±Ρ€Π°ΡƒΠ·Π΅Ρ€Π΅. Он Ρ‚Π°ΠΊΠΆΠ΅ позволяСт ΠΈΡΡΠ»Π΅Π΄ΠΎΠ²Π°Ρ‚ΡŒ (traverse) сущности истории (history entries) прилоТСния. Π­Ρ‚ΠΎ ΡƒΠ»ΡƒΡ‡ΡˆΠ΅Π½Π½Ρ‹ΠΉ Π²Π°Ρ€ΠΈΠ°Π½Ρ‚ ΠΏΡ€Π΅Π΄Ρ‹Π΄ΡƒΡ‰ΠΈΡ… возмоТностСй Π²Π΅Π±-ΠΏΠ»Π°Ρ‚Ρ„ΠΎΡ€ΠΌΡ‹, связанных с Π½Π°Π²ΠΈΠ³Π°Ρ†ΠΈΠ΅ΠΉ, Ρ‚Π°ΠΊΠΈΡ… ΠΊΠ°ΠΊ History API ΠΈ window.location , ΠΊΠΎΡ‚ΠΎΡ€Ρ‹ΠΉ Ρ€Π΅ΡˆΠ°Π΅Ρ‚ ΠΈΡ… ΠΏΡ€ΠΎΠ±Π»Π΅ΠΌΡ‹ ΠΈ ΡΠΏΠ΅Ρ†ΠΈΠ°Π»ΡŒΠ½ΠΎ ΠΏΡ€Π΅Π΄Π½Π°Π·Π½Π°Ρ‡Π΅Π½ для одностраничных ΠΏΡ€ΠΈΠ»ΠΎΠΆΠ΅Π½ΠΈΠΉ (single-page applications, SPA).

    habr.com/ru/companies/timeweb/

    #javascript #js #web_api #webapi #navigation #history #навигация #история #timeweb_ΡΡ‚Π°Ρ‚ΡŒΠΈ #ti

    #ti #timeweb_ΡΡ‚Π°Ρ‚ΡŒΠΈ #история #навигация #history #navigation
  24. Habr @[email protected] Β·

    Navigation API Ρ‚Π΅ΠΏΠ΅Ρ€ΡŒ доступСн Π² Baseline

    Navigation API прСдоставляСт Π²ΠΎΠ·ΠΌΠΎΠΆΠ½ΠΎΡΡ‚ΡŒ ΠΈΠ½ΠΈΡ†ΠΈΠΈΡ€ΠΎΠ²Π°Ρ‚ΡŒ (ΠΏΡ€ΠΎΠ³Ρ€Π°ΠΌΠΌΠ½ΠΎ Π·Π°ΠΏΡƒΡΠΊΠ°Ρ‚ΡŒ), ΠΏΠ΅Ρ€Π΅Ρ…Π²Π°Ρ‚Ρ‹Π²Π°Ρ‚ΡŒ ΠΈ ΡƒΠΏΡ€Π°Π²Π»ΡΡ‚ΡŒ Π½Π°Π²ΠΈΠ³Π°Ρ†ΠΈΠ΅ΠΉ Π² Π±Ρ€Π°ΡƒΠ·Π΅Ρ€Π΅. Он Ρ‚Π°ΠΊΠΆΠ΅ позволяСт ΠΈΡΡΠ»Π΅Π΄ΠΎΠ²Π°Ρ‚ΡŒ (traverse) сущности истории (history entries) прилоТСния. Π­Ρ‚ΠΎ ΡƒΠ»ΡƒΡ‡ΡˆΠ΅Π½Π½Ρ‹ΠΉ Π²Π°Ρ€ΠΈΠ°Π½Ρ‚ ΠΏΡ€Π΅Π΄Ρ‹Π΄ΡƒΡ‰ΠΈΡ… возмоТностСй Π²Π΅Π±-ΠΏΠ»Π°Ρ‚Ρ„ΠΎΡ€ΠΌΡ‹, связанных с Π½Π°Π²ΠΈΠ³Π°Ρ†ΠΈΠ΅ΠΉ, Ρ‚Π°ΠΊΠΈΡ… ΠΊΠ°ΠΊ History API ΠΈ window.location , ΠΊΠΎΡ‚ΠΎΡ€Ρ‹ΠΉ Ρ€Π΅ΡˆΠ°Π΅Ρ‚ ΠΈΡ… ΠΏΡ€ΠΎΠ±Π»Π΅ΠΌΡ‹ ΠΈ ΡΠΏΠ΅Ρ†ΠΈΠ°Π»ΡŒΠ½ΠΎ ΠΏΡ€Π΅Π΄Π½Π°Π·Π½Π°Ρ‡Π΅Π½ для одностраничных ΠΏΡ€ΠΈΠ»ΠΎΠΆΠ΅Π½ΠΈΠΉ (single-page applications, SPA).

    habr.com/ru/companies/timeweb/

    #javascript #js #web_api #webapi #navigation #history #навигация #история #timeweb_ΡΡ‚Π°Ρ‚ΡŒΠΈ #ti

    #ti #timeweb_ΡΡ‚Π°Ρ‚ΡŒΠΈ #история #навигация #history #navigation
  25. Habr @[email protected] Β·

    Navigation API Ρ‚Π΅ΠΏΠ΅Ρ€ΡŒ доступСн Π² Baseline

    Navigation API прСдоставляСт Π²ΠΎΠ·ΠΌΠΎΠΆΠ½ΠΎΡΡ‚ΡŒ ΠΈΠ½ΠΈΡ†ΠΈΠΈΡ€ΠΎΠ²Π°Ρ‚ΡŒ (ΠΏΡ€ΠΎΠ³Ρ€Π°ΠΌΠΌΠ½ΠΎ Π·Π°ΠΏΡƒΡΠΊΠ°Ρ‚ΡŒ), ΠΏΠ΅Ρ€Π΅Ρ…Π²Π°Ρ‚Ρ‹Π²Π°Ρ‚ΡŒ ΠΈ ΡƒΠΏΡ€Π°Π²Π»ΡΡ‚ΡŒ Π½Π°Π²ΠΈΠ³Π°Ρ†ΠΈΠ΅ΠΉ Π² Π±Ρ€Π°ΡƒΠ·Π΅Ρ€Π΅. Он Ρ‚Π°ΠΊΠΆΠ΅ позволяСт ΠΈΡΡΠ»Π΅Π΄ΠΎΠ²Π°Ρ‚ΡŒ (traverse) сущности истории (history entries) прилоТСния. Π­Ρ‚ΠΎ ΡƒΠ»ΡƒΡ‡ΡˆΠ΅Π½Π½Ρ‹ΠΉ Π²Π°Ρ€ΠΈΠ°Π½Ρ‚ ΠΏΡ€Π΅Π΄Ρ‹Π΄ΡƒΡ‰ΠΈΡ… возмоТностСй Π²Π΅Π±-ΠΏΠ»Π°Ρ‚Ρ„ΠΎΡ€ΠΌΡ‹, связанных с Π½Π°Π²ΠΈΠ³Π°Ρ†ΠΈΠ΅ΠΉ, Ρ‚Π°ΠΊΠΈΡ… ΠΊΠ°ΠΊ History API ΠΈ window.location , ΠΊΠΎΡ‚ΠΎΡ€Ρ‹ΠΉ Ρ€Π΅ΡˆΠ°Π΅Ρ‚ ΠΈΡ… ΠΏΡ€ΠΎΠ±Π»Π΅ΠΌΡ‹ ΠΈ ΡΠΏΠ΅Ρ†ΠΈΠ°Π»ΡŒΠ½ΠΎ ΠΏΡ€Π΅Π΄Π½Π°Π·Π½Π°Ρ‡Π΅Π½ для одностраничных ΠΏΡ€ΠΈΠ»ΠΎΠΆΠ΅Π½ΠΈΠΉ (single-page applications, SPA).

    habr.com/ru/companies/timeweb/

    #javascript #js #web_api #webapi #navigation #history #навигация #история #timeweb_ΡΡ‚Π°Ρ‚ΡŒΠΈ #ti

    #javascript #js #web_api #webapi #navigation #history
  26. iamdtms @iamdtms Β·

    web-features-cli
    npmjs.com/package/web-features

    #js #npm
  27. iamdtms @[email protected] Β·

    web-features-cli #npm #js
    npmjs.com/package/web-features

    #js #npm
  28. iamdtms @[email protected] Β·

    web-features-cli #npm #js
    npmjs.com/package/web-features

    #js #npm
  29. iamdtms @[email protected] Β·

    web-features-cli #npm #js
    npmjs.com/package/web-features

    #js #npm
  30. iamdtms @[email protected] Β·

    web-features-cli #npm #js
    npmjs.com/package/web-features

    #js #npm
  31. Guerz @Guerz Β·

    the i'm learning from: (spine), iOS app (refresher), (reference), for notes, for building.

    16-week roadmap: β†’ β†’ β†’ β†’ β†’ β†’ β†’ .js β†’

    the self-admin structure forces honesty β€” no one's grading you. the work either happened or it didn't.

    week 1: it happened.

    weekly at: blogguerz.wordpress.com

    #stack #freecodecamp #encode #w3schools #scrimba #obsidian
  32. github.com/ghostwriter @[email protected] Β·

    Upgrade immediately.

    #NextJs: 15.5.18, 16.2.6

    #React: 19.0.6, 19.1.7, 19.2.6 for the react-server-dom-parcel, react-server-dom-webpack and react-server-dom-turbopack packages

    vercel.com/changelog/next-js-m

    Vulnerability:

    - Middleware and proxy bypass
    - Denial of service
    - Server-side request forgery
    - Cache poisoning
    - Cross-site scripting

    #Vercel #CVE #RCE #JS #NPM #AI #Security #Vulnerability #AISlop

    #nextjs #react #vercel #cve #rce #js
  33. github.com/ghostwriter @[email protected] Β·

    Upgrade immediately.

    #NextJs: 15.5.18, 16.2.6

    #React: 19.0.6, 19.1.7, 19.2.6 for the react-server-dom-parcel, react-server-dom-webpack and react-server-dom-turbopack packages

    vercel.com/changelog/next-js-m

    Vulnerability:

    - Middleware and proxy bypass
    - Denial of service
    - Server-side request forgery
    - Cache poisoning
    - Cross-site scripting

    #Vercel #CVE #RCE #JS #NPM #AI #Security #Vulnerability #AISlop

    #nextjs #react #vercel #cve #rce #js
  34. github.com/ghostwriter @[email protected] Β·

    Upgrade immediately.

    #NextJs: 15.5.18, 16.2.6

    #React: 19.0.6, 19.1.7, 19.2.6 for the react-server-dom-parcel, react-server-dom-webpack and react-server-dom-turbopack packages

    vercel.com/changelog/next-js-m

    Vulnerability:

    - Middleware and proxy bypass
    - Denial of service
    - Server-side request forgery
    - Cache poisoning
    - Cross-site scripting

    #Vercel #CVE #RCE #JS #NPM #AI #Security #Vulnerability #AISlop

    #nextjs #react #vercel #cve #rce #js
  35. github.com/ghostwriter @[email protected] Β·

    Upgrade immediately.

    #NextJs: 15.5.18, 16.2.6

    #React: 19.0.6, 19.1.7, 19.2.6 for the react-server-dom-parcel, react-server-dom-webpack and react-server-dom-turbopack packages

    vercel.com/changelog/next-js-m

    Vulnerability:

    - Middleware and proxy bypass
    - Denial of service
    - Server-side request forgery
    - Cache poisoning
    - Cross-site scripting

    #Vercel #CVE #RCE #JS #NPM #AI #Security #Vulnerability #AISlop

    #aislop #vulnerability #security #ai #npm #js
  36. github.com/ghostwriter @[email protected] Β·

    Upgrade immediately.

    #NextJs: 15.5.18, 16.2.6

    #React: 19.0.6, 19.1.7, 19.2.6 for the react-server-dom-parcel, react-server-dom-webpack and react-server-dom-turbopack packages

    vercel.com/changelog/next-js-m

    Vulnerability:

    - Middleware and proxy bypass
    - Denial of service
    - Server-side request forgery
    - Cache poisoning
    - Cross-site scripting

    #Vercel #CVE #RCE #JS #NPM #AI #Security #Vulnerability #AISlop

    #nextjs #react #vercel #cve #rce #js
  37. tonysull @[email protected] Β·

    I'd really like a #js package manager that vendors everything. Track a snapshot of a git commit and give me a diff view to review when I update a dependency

    This may mean we couldn't really distribute pre-built packages, but that's a good thing IMO

    πŸ”— tonysull.co/posts/i-d-really-l

    #js
  38. tonysull @[email protected] Β·

    I'd really like a #js package manager that vendors everything. Track a snapshot of a git commit and give me a diff view to review when I update a dependency

    This may mean we couldn't really distribute pre-built packages, but that's a good thing IMO

    πŸ”— tonysull.co/posts/i-d-really-l

    #js
  39. tonysull @[email protected] Β·

    I'd really like a #js package manager that vendors everything. Track a snapshot of a git commit and give me a diff view to review when I update a dependency

    This may mean we couldn't really distribute pre-built packages, but that's a good thing IMO

    πŸ”— tonysull.co/posts/i-d-really-l

    #js
  40. tonysull @[email protected] Β·

    I'd really like a #js package manager that vendors everything. Track a snapshot of a git commit and give me a diff view to review when I update a dependency

    This may mean we couldn't really distribute pre-built packages, but that's a good thing IMO

    πŸ”— tonysull.co/posts/i-d-really-l

    #js
  41. tonysull @[email protected] Β·

    I'd really like a #js package manager that vendors everything. Track a snapshot of a git commit and give me a diff view to review when I update a dependency

    This may mean we couldn't really distribute pre-built packages, but that's a good thing IMO

    πŸ”— tonysull.co/posts/i-d-really-l

    #js
  42. tonysull @[email protected] Β·

    🌢️ The #js ecosystem should never have moved to building and/or bundling shared packages

    Building, bundling, tree shaking, etc are consumer concerns, not publisher concerns

    Ship your source, only support #esm these days, and let the end user deal with the rest

    πŸ”— tonysull.co/posts/the-js-ecosy

    #js #esm
  43. tonysull @[email protected] Β·

    🌢️ The #js ecosystem should never have moved to building and/or bundling shared packages

    Building, bundling, tree shaking, etc are consumer concerns, not publisher concerns

    Ship your source, only support #esm these days, and let the end user deal with the rest

    πŸ”— tonysull.co/posts/the-js-ecosy

    #js #esm
  44. tonysull @[email protected] Β·

    🌢️ The #js ecosystem should never have moved to building and/or bundling shared packages

    Building, bundling, tree shaking, etc are consumer concerns, not publisher concerns

    Ship your source, only support #esm these days, and let the end user deal with the rest

    πŸ”— tonysull.co/posts/the-js-ecosy

    #js #esm
  45. tonysull @[email protected] Β·

    🌢️ The #js ecosystem should never have moved to building and/or bundling shared packages

    Building, bundling, tree shaking, etc are consumer concerns, not publisher concerns

    Ship your source, only support #esm these days, and let the end user deal with the rest

    πŸ”— tonysull.co/posts/the-js-ecosy

    #esm #js
  46. tonysull @[email protected] Β·

    🌢️ The #js ecosystem should never have moved to building and/or bundling shared packages

    Building, bundling, tree shaking, etc are consumer concerns, not publisher concerns

    Ship your source, only support #esm these days, and let the end user deal with the rest

    πŸ”— tonysull.co/posts/the-js-ecosy

    #js #esm
  47. Till @[email protected] Β·

    Say you're building a moderately complex app with e.g. Hono/Express.js. I don't want next, react etc.. How do you organise handlers/routes, etc.? Are there any good primers for how to modularise the application? #javascript #js #ts

    #javascript #js #ts
  48. Till @[email protected] Β·

    Say you're building a moderately complex app with e.g. Hono/Express.js. I don't want next, react etc.. How do you organise handlers/routes, etc.? Are there any good primers for how to modularise the application? #javascript #js #ts

    #javascript #js #ts
  49. Till @[email protected] Β·

    Say you're building a moderately complex app with e.g. Hono/Express.js. I don't want next, react etc.. How do you organise handlers/routes, etc.? Are there any good primers for how to modularise the application? #javascript #js #ts

    #javascript #js #ts
  50. Till @[email protected] Β·

    Say you're building a moderately complex app with e.g. Hono/Express.js. I don't want next, react etc.. How do you organise handlers/routes, etc.? Are there any good primers for how to modularise the application? #javascript #js #ts

    #ts #js #javascript