Python framework Django 5.0 was released on Monday, which means it’s time to update if you’re running 4.1.
This release included three major changes, according to the blog post announcing it. The first is that the database-computed default values now allow for defining database-computed defaults to model fields. Second, the Django ORM was expanded such that the generated model field allows the creation of database-generated columns. Finally, form field rendering was simplified by adding a field group to the templates system.
Django 4.2 will receive security and data loss fixes until April 2026. The team is encouraging users to upgrade before then so as to not miss any security fixes. There’s more about the supported versions on the download page.
Storybook Releases Last Update before Version 8
Storybook issued its final release — version 7.6 — before Storybook 8, which will be the next major release. Storybook is a frontend tool designed for UI development. Among the changes included in this update was a switch from Babel to the Speedy Web Compiler, which all new Webpack projects other than Angular will now use. Michael Shilman, project lead at Storybook, explained the changes available with the Storybook 7.6 release, which includes:
Adding SWC support, avif support and other fixes for Next.js, so thatStorybook is faster and matches Next.js behavior more closely;
New testing utilities and a faster build mode that reduces static build times when testing;
New experimental SvelteKit mocks, which can be used to safely write stories for any components that import SvelteKit-specific modules, such as navigation functions. Also included are bug fixes for Svelte decorators and Storybook will no longer run decorators twice; and
React-docgen upgrade. ”A major performance upgrade in Storybook 8 will be the switch to react-docgen for autogenerated controls,” Shilman wrote. “This might sound small but it will speed up startup times by 2x or more.”
There’s also a new Storybook doctor command that performs general project health checks such as finding mismatching Storybook versions, duplicate dependencies and incompatible add-ons.
Node.js Version 20 in Beta
Vercel will depreciate Node.js 16 for builds and functions on Feb. 6. Its end of life was Sept. 11. This news comes on the heels of last month’s beta release of Node.js version 20 LTS.
Node.js version 20 can be used as the runtime for builds and serverless functions. Among the new features introduced with version 20 are a new experimental permission model, synchronous import.meta.resolve, stable test runner and performance updates to the V8 JavaScript Engine and the URL parser, Ada.
JetBrains Updates Its IDEs
Earlier this week, The New Stack covered JetBrains’ release of a new AI Assistant, but that wasn’t the only news coming out of the IDE company on Wednesday. JetBrains also released the 2023.3 updates to its IDEs:
IntelliJ IDEA 2023.3: It now has full support for the latest Java 21 features. Other updates include additions such as virtual threads, record patterns, pattern matching for switch expressions, and sequenced collections. Users can now deploy, debug and manage Kubernetes clusters from within the IDE with IntelliJ IDEA. Also with this release, support for new Kotlin versions is delivered together with IntelliJ IDEA and Android Studio updates, meaning that developers no longer need to update the Kotlin plugin from JetBrains Marketplace.
PyCharm 2023.3: Users can preview Django templates while editing them and see all changes to them with a server Rerun. They also added support for Python 3.12.
WebStorm 2023.3: Webstorm has improved support for Angular, Vue, Svelte, and TypeScript improvements. There’s also initial support for the native Node.js test runner.
Ingress Platform Releases JavaScript, Python SDK
Ngrok is a unified ingress platform for developers, and on Wednesday it released new SDKs for JavaScript and Python. The SDKs will allow developers to serve their applications and manage traffic by embedding ingress with a “single line of code,” the company stated.
Developers can use the SDKs to establish API-defined contracts that dictate the expected behavior between their applications and the ingress layer, which manages incoming traffic to a system or network and includes functions such as traffic routing, load balancing and security. Use case cases for ngrok’s SDk include managing ingress to developer environments, ingress to APIs, and ingress to APIs on devices that run on external networks.
“Today, there is an implicit, hidden dependency between the application and the infrastructure that delivers it, such as load balancers and reverse proxies,” the company wrote. “Declaring ingress directly in the application itself radically simplifies the development process by defining the ingress functionality that includes non-functional capabilities such as high performance, resiliency, security and observability needed to deliver their software correctly.”
TRENDING STORIES
YOUTUBE.COM/THENEWSTACK
Tech moves fast, don't miss an episode. Subscribe to our YouTube channel to stream all our podcasts, interviews, demos, and more.
Loraine Lawson is a veteran technology reporter who has covered technology issues from data integration to security for 25 years. Before joining The New Stack, she served as the editor of the banking technology site Bank Automation News. She has...