EPMUII-10641
EPMUII-10641
jQuery
TC39
CSS
Signals
SVG
AI
HTML
Angular
Caching
Front-End
JavaScript
Lambda
Law
Licenses
NextJS
Logging
NodeJS
Offline
VueJS
Podcasting
RxJS
ReactJS
Python
Testing
PostgreSQL
EPMUII-10641
EPMUII-10641
External content
Peter Pistorius on Developing RedwoodSDK
In this episode of ShopTalk Show, Dave Rupert and Chris Coyier host Peter Pistorius, diving into the evolution of RedwoodJS into the new RedwoodSDK. They explore: - The strategic shift from RedwoodJS to RedwoodSDK and its impact on developer experience - Redesigned routing model and seamless integration with Cloudflare Workers - Fresh marketing angles and slogans shaping RedwoodSDK’s identity - How Peter’s cultural background influenced the SDK’s guiding principles - Community reception and feedback since the transition - Future monetization plans to sustainably support the project
External content
🕹️ Odyc.js: A JS Library for Pixel Games/Stories
Odyc.js is a compact JavaScript library (with an 8-bit Game Boy Color vibe) that lets you create narrative pixel games directly in the browser—no complex setup needed. You can build and play games entirely in an online playground, complete with code examples showcasing pixel art, sound, text, and simple game logic .
External content
The State of React and the Community in 2025
The piece offers a thorough exploration of React’s evolution, community dynamics, and confusion around its development. It explains that React remains the most-used UI library and recently launched version 19—featuring stable Server Components and a new use promise hook—while older APIs have been removed. The author—Redux maintainer Mark Erikson—draws from his long involvement in the ecosystem to clarify motivations behind major architectural decisions, from React Server Components to relationship shifts with Meta and Vercel/Next.js. Notably, the article addresses widespread community concerns—like perceived bias toward Next.js, confusion over using React without full frameworks, and gaps in documentation—explaining these issues and dispelling much of the FUD. Erikson ultimately credits React's maintainers for solidifying the library’s direction and urges improved transparency, communication, and community documentation collaboration.
External content
How JavaScript Was Written Back in the Day
Trevor Lasn revisits legacy JavaScript code from the 2006–2015 pre-ES6 era, reflecting on its quirks and the challenges it presents today. He discusses how older JavaScript patterns, coding styles, and tools shaped development before modern features like modules and arrow functions became standard. The post highlights both the limitations and nostalgic aspects of this period, providing insight into how far JavaScript has evolved.
External content
#072 - The Frozen Arch, Killing my App & React Native World Domination
In this episode of Rocket Ship, hosts and guest Simon Grimm discuss highlights from AppJS 2025 and react to major talks shaping the future of React Native. They cover: - Frozen architecture: what it means for app updates and maintainability. - Why Simon decided to “kill” his existing app and build anew. - Fresh React Native news and exciting new packages showcased at the event. - “World domination” ambitions: how React Native is pushing for broader adoption and innovation. This episode blends conference tidbits, personal journeys, technical insights, and community updates—all in a lively, 23-minute format.
External content
pnpm 10.12 Introduces an Experimental Global Virtual Store
pnpm v10.12 builds on its reputation for speed and efficiency over npm by introducing a new global virtual store feature. Instead of installing dependencies separately for each project, pnpm creates a shared global store that projects link to via node_modules, cutting down redundant installations and saving disk space. The update also enhances version catalogs for managing dependencies in monorepos. New options allow better control over pinned versions and simplify adding dependencies to catalogs, making it easier to maintain consistent dependency versions across large projects. Additional improvements include better CI detection, improved cache management, and clearer error messages, all aimed at boosting developer productivity and streamlining package management workflows.
External content
If Statements in CSS?
In Syntax Podcast #910, hosts Wes Bos and Scott Tolinski delve into the newly introduced `if()` function in CSS, exploring its functionality, use cases, and implications for web development. Key Topics Discussed: - Introduction of `if()` in CSS: The hosts examine the recent addition of the `if()` function in CSS, which allows for conditional styling based on attribute values. This feature enables styles to be applied conditionally without the need for JavaScript. - Practical Applications: They discuss scenarios where the `if()` function can be utilized, such as toggling themes or applying styles based on user preferences, enhancing the flexibility of CSS. - Syntax and Usage: The episode covers the syntax of the `if()` function, providing examples and best practices for its implementation in real-world projects. - Comparison with JavaScript: The hosts compare the new CSS functionality with traditional JavaScript-based conditional styling, highlighting the advantages and limitations of each approach. - Future of CSS: They speculate on the potential evolution of CSS towards more declarative and logic-driven stylesheets, discussing how this aligns with broader trends in web development.
External content
Suppressions of Suppressions
The author discusses the risks of silencing linter rules in codebases. While developers often disable rules they find too strict or irrelevant, these suppressions can hide serious bugs and degrade code quality over time. Dan Abramov argues for adding a rule that forbids disabling the most critical linter checks, ensuring essential protections remain enforced. The article highlights the balance between flexibility and safety in maintaining clean, reliable code and encourages thoughtful use of linter suppressions.
External content
Announcing Oxlint 1.0: The Super Fast Linter
First appearing just 18 months ago, Oxlint has made an impact as an incredibly fast Rust-powered linter for JavaScript and TypeScript—boasting a 50–100× performance improvement over ESLint while supporting hundreds of its rules. Now, it’s gone stable. Version 1.0 delivers 500+ rules, seamless integration with popular editors and CI tools, and requires no configuration to get started. Major companies like Airbnb, Mercedes-Benz, and Sentry are already using it, with CI pipelines reportedly running up to 80× faster. Though custom rule support isn't available yet, it's on the roadmap, along with better error messages and configuration options.
External content
Handling and Throwing Errors
In Syntax Podcast #909, hosts Wes Bos and Scott Tolinski delve into best practices for handling errors in JavaScript and TypeScript. They discuss: - Error Terminology: Understanding the distinction between throwing and catching errors. - Error Components: Breaking down the structure of an error, including name, message, and stack trace. - Throwing Errors: Guidelines on when and how to throw errors effectively. - Promise Errors: Strategies for handling errors in asynchronous code using try...catch, .catch(), and finally. - Re-throwing Errors: Techniques for propagating errors and using the Error.cause property. - Client-Side Errors: Approaches for catching, displaying, and transforming server errors on the client side, including the use of error boundaries. - Server-Side Errors: Best practices for handling errors in server responses, including JSON APIs and HTTP status codes. - Logging and Solving Errors: Utilizing tools like Sentry for error tracking and resolution. - TypeScript and Errors: Leveraging TypeScript's type system to manage errors more effectively.
The Morning Ritual: Personal Content with a Cup of Tea
Savoring JavaScript articles with morning tea, developers seamlessly blend relaxation and professional growth.
Do You Need a University to Get a Job in IT?
Positions in the field of information technology are mostly experience-based. Many of these positions demand a university degree or certificate program as minimal education requirements.
To FR Media Authors: How to Write an Article Using Markdown
When creating content on the FR Media portal, Markdown can be a powerful tool to structure your articles quickly and efficiently.
FR Media Portal: Leading the Future of IT Content
FR Media Platform's primary mission is to provide a space for content creators to share their work and for users to find personalized content.
CodeNodes // Node.js & NestJS Series [Gdańsk]
June, 26
16:00UTC+00:00(UTC)
![CodeNodes // Node.js & NestJS Series [Gdańsk]](https://prod-frmedia-digital-asset-management.s3.eu-central-1.amazonaws.com/medium_Slide_16_9_336_5435e03e05.jpg)
JSCraftCamp
June, 27
07:00UTC+00:00(UTC)
enterJS Advanced Angular Day
July, 01
07:00UTC+00:00(UTC)
Online
React Nexus
July, 03
04:00UTC+00:00(UTC)
