<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Web Development - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Web Development News feed</description>
    <item>
      <title>Varlock Releases Bumpy: A File-Based Versioning Alternative to Changesets</title>
      <link>https://www.infoq.com/news/2026/11/bumpy-changesets-alternative/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Web+Development-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/11/bumpy-changesets-alternative/en/headerimage/generatedHeaderImage-1793973539308.jpg"/&gt;&lt;p&gt;Bumpy is an MIT-licensed, TypeScript tool for version management and changelogs in monorepos. It follows the changesets workflow, using markdown bump files, and adds support for workspace and catalog protocols, custom publish commands, and branch-based prereleases. Changesets v3, released in August 2026, closed many earlier gaps, though differences remain.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>Web Development</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Sat, 07 Nov 2026 06:54:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/11/bumpy-changesets-alternative/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Web+Development-news</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-11-07T06:54:00Z</dc:date>
      <dc:identifier>/news/2026/11/bumpy-changesets-alternative/en</dc:identifier>
    </item>
    <item>
      <title>TypeScript 7.1 Beta: Restores the Compiler API and Makes Vue and Svelte First-Class</title>
      <link>https://www.infoq.com/news/2026/11/typescript-7-1-beta/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Web+Development-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/11/typescript-7-1-beta/en/headerimage/generatedHeaderImage-1793901816316.jpg"/&gt;&lt;p&gt;TypeScript 7.1 Beta, announced October 20, 2026, restores the compiler API removed in 7.0, now split into separate entry points. It adds content mappers, letting tools like Vue check non-standard files. One Vue project's type checks fell from 14.19 to 3.10 seconds. An editor issue remains open, and teams may need TypeScript 6 alongside 7.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>JavaScript</category>
      <category>Web Development</category>
      <category>Svelte</category>
      <category>TypeScript</category>
      <category>Vue.js</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Fri, 06 Nov 2026 11:06:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/11/typescript-7-1-beta/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Web+Development-news</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-11-06T11:06:00Z</dc:date>
      <dc:identifier>/news/2026/11/typescript-7-1-beta/en</dc:identifier>
    </item>
    <item>
      <title>Vitest 5: Prioritises Performance with a Shared Vite Server, Trace View, and Stricter Test Defaults</title>
      <link>https://www.infoq.com/news/2026/11/vite-5-release/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Web+Development-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/11/vite-5-release/en/headerimage/generatedHeaderImage-1793723335877.jpg"/&gt;&lt;p&gt;Vitest 5.0 focuses on speed, with reported gains of 8 to 25 percent in most setups and up to 53 percent in VM pools. It adds a vitest doctor command, Browser Mode Trace View, and vi.when. Defaults are stricter: clearMocks is true and unawaited async assertions fail. It requires Vite 6.4 and Node.js 22.12 or newer.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>Web Development</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Tue, 03 Nov 2026 16:47:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/11/vite-5-release/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Web+Development-news</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-11-03T16:47:00Z</dc:date>
      <dc:identifier>/news/2026/11/vite-5-release/en</dc:identifier>
    </item>
    <item>
      <title>Chrome Opens Trial for the Email Verification API: Letting Sites Verify without Sending Emails</title>
      <link>https://www.infoq.com/news/2026/10/chrome-email-verification/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Web+Development-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/10/chrome-email-verification/en/headerimage/generatedHeaderImage-1793091215457.jpg"/&gt;&lt;p&gt;Google has opened a Chrome origin trial for the Email Verification API, a WICG proposal that lets the browser confirm email ownership without sending a message. Gmail is the first provider. Developers add form hints and validate a signed token server-side. Commenters question the privacy benefit, and the API is best used as a progressive enhancement.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>JavaScript</category>
      <category>Web Development</category>
      <category>Google</category>
      <category>Email</category>
      <category>TypeScript</category>
      <category>Chrome</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Wed, 28 Oct 2026 09:32:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/10/chrome-email-verification/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Web+Development-news</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-10-28T09:32:00Z</dc:date>
      <dc:identifier>/news/2026/10/chrome-email-verification/en</dc:identifier>
    </item>
  </channel>
</rss>
