You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to access environment variables after connecting Netlify to bolt.new, the Variables tab of a Stackblitz user's settings throws a "cannot read properties of null" error causing the variables page to crash.
Version = 1.84.0
Hash = 3b0b7194bc6b567c2eaf4c96a5759098469dcf59
WebContainer = fc837ba8
Browser name = Chrome
Full version = 131.0.0.0
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 Edg/131.0.0.0
performance.memory = {
"totalJSHeapSize": 108085580,
"usedJSHeapSize": 104588028,
"jsHeapSizeLimit": 4294705152
}
Maybe this is an issue that belongs in https://github.com/stackblitz/bolt.new, I'm not sure. It's either bolt.new didn't set all the proper information when an app gets connected in bolt, or the variables page in Stackblitz needs to be adjusted to handle connected apps, or maybe connected apps shouldn't even be getting loaded in the Variables page on Stackblitz. 🤔
Describe the bug
Description
When attempting to access environment variables after connecting Netlify to bolt.new, the Variables tab of a Stackblitz user's settings throws a "cannot read properties of null" error causing the variables page to crash.
Link to the blitz that caused the error
https://stackblitz.com/~/github.com/nickytonline/nickyt.online?file=astro.config.mjs&view=editor
Steps to reproduce
Load a project in StackBlitz that requires environment variables
Navigate to bolt.new settings
Connect and authorize Netlify integration
Attempt to access environment variables, https://stackblitz.com/settings/variables
Page crashes
Expected behavior
Parity with Local
Screenshots
stackblitz.mp4
Platform
Additional context
https://bsky.app/profile/nickyt.online/post/3lcisbxscrc2l
The text was updated successfully, but these errors were encountered: