<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bolt.new fixes from Vibe Coder Daily</title><description>New Bolt.new fixes: what breaks, why it happens, and the exact steps that fix it.</description><link>https://vibecoderdaily.com/tools/bolt/</link><language>en</language><atom:link href="https://vibecoderdaily.com/tools/bolt/rss.xml" rel="self" type="application/rss+xml"/><item><title>Why that npm package won&apos;t install in Bolt.new (it&apos;s not your code)</title><link>https://vibecoderdaily.com/blog/bolt-native-npm-package-webcontainer-fix/</link><guid isPermaLink="true">https://vibecoderdaily.com/blog/bolt-native-npm-package-webcontainer-fix/</guid><description>Bolt.new can&apos;t install packages like bcrypt, sqlite3, or canvas — not because of a bug, but because it runs Node inside a browser sandbox that blocks native addons. Here&apos;s why, how to spot it, and which pure-JS or hosted alternative to reach for instead.</description><pubDate>Wed, 09 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Your Bolt.new app crashed after deploy — the environment variable gap nobody warns you about</title><link>https://vibecoderdaily.com/blog/bolt-env-variables-deploy-crash-fix/</link><guid isPermaLink="true">https://vibecoderdaily.com/blog/bolt-env-variables-deploy-crash-fix/</guid><description>Bolt.new apps that work perfectly in preview often crash the moment they&apos;re deployed, because environment variables set in Bolt&apos;s Secrets panel don&apos;t automatically transfer to Netlify or Vercel. Here&apos;s why, how to spot it, and the fix.</description><pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate></item></channel></rss>