feat(simulator): integrate Sentry error tracking (#4962) #391
Conversation
- Add Sentry configuration with environment-specific settings - Configure error tracking and performance monitoring - Add proper canvas initialization - Enable component tracking and error sampling Fixes #4962
Implement error monitoring and performance tracking for the simulator: - Add Sentry configuration with environment-specific settings - Fix canvas initialization and error handling - Configure error sampling and component tracking - Enable performance monitoring for Vue components Closes #4962
WalkthroughThe changes in this pull request involve the addition of environment variables in the Changes
Assessment against linked issues
Poem
Warning Rate limit exceeded@AdityaP700 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 9 minutes and 13 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
❌ Deploy Preview for circuitverse failed.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 12
🧹 Outside diff range and nitpick comments (6)
src/pages/simulator.vue (1)
37-43: Consider adding z-index for proper canvas layeringWhile the absolute positioning ensures full coverage, consider adding a z-index to prevent potential rendering issues with other absolutely positioned elements.
.simulation-canvas { position: absolute; top: 0; left: 0; width: 100%; height: 100%; + z-index: 1; }src/simulator/src/simulationArea.ts (3)
34-37: Consider using requestAnimationFrame for better timing accuracyThe current implementation using setTimeout may lead to timing drift. Consider these improvements:
- Use requestAnimationFrame for more precise timing
- Add error handling around clockTick
- Implement a cleanup mechanism to prevent memory leaks
timer() { - if (this.clockEnabled) { - clockTick(); - } - setTimeout(() => this.timer(), this.timePeriod); + let lastTick = performance.now(); + const tick = (now: number) => { + if (this.clockEnabled && (now - lastTick) >= this.timePeriod) { + try { + clockTick(); + lastTick = now; + } catch (error) { + console.error('Error in clock tick:', error); + } + } + this.animationFrame = requestAnimationFrame(tick); + }; + this.animationFrame = requestAnimationFrame(tick); }
58-62: Improve input validation and clock state managementThe current implementation could benefit from more robust validation and explicit state management.
-changeClockTime(t: number) { - if (t < 50) return; - this.timePeriod = t; - this.clockEnabled = true; +changeClockTime(t: number) { + if (!Number.isFinite(t)) { + throw new Error('Time period must be a finite number'); + } + if (t < 50) { + throw new Error('Time period must be at least 50ms'); + } + if (t > 5000) { + throw new Error('Time period cannot exceed 5000ms'); + } + this.timePeriod = t; }
64-68: LGTM: Proper null checking implementedThe null checks for both context and canvas are good. Consider adding error tracking for debugging when clearing fails.
clear() { if (this.context && this.canvas) { this.context.clearRect(0, 0, this.canvas.width, this.canvas.height); + } else { + Sentry.captureMessage('Failed to clear canvas: context or canvas is null'); } }src/main.ts (2)
36-42: Reconsider discarding Sentry events in non-production environmentsIn the
beforeSendfunction, events are discarded in non-production environments by returningnull. This means that errors occurring in development or staging environments will not be sent to Sentry. If the intention is to monitor errors across all environments, consider modifying the condition.Apply this diff to send events in all environments while still logging errors to the console in non-production:
36 beforeSend(event) { 37 if (!isProd) { 38 console.error('Sentry error:', event); -39 return null; 40 } 41 return event; 42 },
35-35: EnsureVITE_APP_VERSIONis defined to accurately track releasesCurrently, the
releaseis set toimport.meta.env.VITE_APP_VERSION || '1.0.0'. IfVITE_APP_VERSIONis not defined, it will default to'1.0.0', which may cause confusion in release tracking. Ensure thatVITE_APP_VERSIONis correctly set in your environment variables to accurately reflect the application version in Sentry.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (7)
.env(1 hunks)package.json(2 hunks)sentry.properties(1 hunks)src/main.ts(2 hunks)src/pages/simulator.vue(1 hunks)src/simulator/src/simulationArea.ts(2 hunks)vite.config.ts(3 hunks)
✅ Files skipped from review due to trivial changes (1)
- .env
🧰 Additional context used
🪛 eslint
src/pages/simulator.vue
[error] 19-19: 'defineComponent' is defined but never used.
(no-unused-vars)
🔇 Additional comments (7)
src/pages/simulator.vue (2)
2-12: LGTM! Well-structured template with proper component organization.
The template structure provides good separation of concerns with the simulation canvas properly isolated from other components.
23-32: Excellent implementation of robust canvas initialization!
The implementation effectively addresses the canvas context errors mentioned in the PR objectives by:
- Using
nextTickto ensure DOM updates are complete - Implementing proper null checks for the canvas element
- Verifying the 2D context before simulator setup
This should resolve the TypeError that affected 44 events across 11 users.
src/simulator/src/simulationArea.ts (2)
6-6: LGTM: Proper initialization of canvas property
Initializing canvas to null enables explicit existence checks, which aligns with fixing the canvas context errors mentioned in the PR objectives.
Line range hint 6-68: Verify canvas error handling coverage
Let's ensure we've caught all potential canvas-related errors that could occur during simulation.
vite.config.ts (2)
6-6: LGTM!
The Sentry Vite plugin import is correctly placed and follows TypeScript conventions.
27-33: Verify Sentry configuration completeness
Let's verify the Sentry setup across the project:
Also applies to: 46-46
✅ Verification successful
Let me gather more information about the Sentry configuration.
Let me check the Sentry initialization in the main.ts file since we found its import there.
Sentry configuration is properly set up and complete
The Sentry configuration is correctly implemented with:
- Complete initialization in main.ts with proper DSN, environment settings, and error handling
- Production vs development environment handling
- Source map configuration in vite.config.ts and tsconfig.json
- Required dependencies in package.json (@sentry/vue, @sentry/tracing)
The auth token configuration in vite.config.ts is correctly set up to be provided via environment variables, which is the recommended secure approach.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify Sentry configuration completeness
# Check for required environment variables in .env files
echo "Checking .env files for Sentry configuration..."
rg -l "SENTRY" --type env
# Check for consistent Sentry initialization across the project
echo "Checking Sentry initialization in source files..."
rg "Sentry.init" --type ts --type vue
# Check for other source map configurations that might conflict
echo "Checking for conflicting source map configurations..."
rg "sourcemap|sourceMap" --type json --type ts
Length of output: 1500
Script:
#!/bin/bash
# Check for .env and example env files
echo "Checking for .env files..."
fd -t f "\.env" -E "node_modules"
# Check for Sentry imports and configuration
echo "Checking Sentry imports and configuration..."
rg "@sentry" -A 3
# Check for main.ts or similar entry files that might contain Sentry initialization
echo "Checking entry files..."
fd "main.ts|index.ts"
# Check package.json for Sentry dependencies
echo "Checking Sentry dependencies..."
cat package.json | grep -i "sentry"
Length of output: 27304
Script:
#!/bin/bash
# Check Sentry initialization in main.ts
echo "Checking Sentry initialization in main.ts..."
cat src/main.ts
# Check for environment variable files
echo -e "\nChecking for environment files..."
fd "\.env" --no-ignore
# Check for Sentry configuration in other potential locations
echo -e "\nChecking for additional Sentry configuration..."
rg "Sentry\.init|SENTRY" --type ts
Length of output: 1907
package.json (1)
18-19: Verify security of Sentry package versions
Let's ensure the selected versions of Sentry packages are secure and up-to-date.
Also applies to: 49-50
✅ Verification successful
Consider updating Sentry packages to latest stable versions
The current versions can be updated:
@sentry/tracing: 7.114.0 → 7.120.0@sentry/vue: 8.40.0 → 8.41.0-beta.0 (Note: current version is stable, beta update not recommended)
No security vulnerabilities were found in any of the Sentry packages. The current versions are reasonably recent and secure.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for security advisories and latest versions of Sentry packages
# Check npm for latest versions and security advisories
for package in @sentry/tracing @sentry/vue @sentry/cli @sentry/vite-plugin; do
echo "Checking $package..."
npm view $package versions --json | jq -r '.[-1]'
# Check for known vulnerabilities using GitHub API
gh api graphql -f query='{
securityVulnerabilities(first: 5, ecosystem: NPM, package: "'${package}'") {
nodes {
advisory {
summary
severity
publishedAt
}
vulnerableVersionRange
firstPatchedVersion {
identifier
}
}
}
}'
done
Length of output: 2324
sentry.properties
Outdated
| defaults.org=circuitverse | ||
| defaults.project=javascript-vue |
There was a problem hiding this comment.
Remove duplicate configuration entries
The organization and project settings are duplicated. Remove the duplicate entries to maintain a single source of truth.
Remove these duplicate lines as they're already defined above:
-defaults.org=circuitverse
-defaults.project=javascript-vueCommittable suggestion skipped: line range outside the PR's diff.
- Remove exposed auth token and use environment variable - Align Sentry package versions - Restrict sourcemaps to development - Add environment variable examples - Clean up configuration files
…tyaP700/cv-frontend-vue into feat/sentry-integration-4962
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (1)
sentry.properties (1)
1-5: Consider adding optional configuration settings.For better error tracking and deployment management, consider adding these optional settings:
defaults.url=https://sentry.io/ defaults.org=circuitverse defaults.project=javascript-vue auth.token=${SENTRY_AUTH_TOKEN} cli.executable=node_modules/@sentry/cli/bin/sentry-cli +defaults.environment=${NODE_ENV} +defaults.dist=${npm_package_version} +defaults.deploy-env=${DEPLOY_ENV}These additions would help in:
- Distinguishing errors between different environments
- Tracking errors across different versions
- Managing deployment-specific configurations
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (4)
.env.example(1 hunks)package.json(2 hunks)sentry.properties(1 hunks)vite.config.ts(3 hunks)
✅ Files skipped from review due to trivial changes (1)
- .env.example
🚧 Files skipped from review as they are similar to previous changes (1)
- package.json
🔇 Additional comments (4)
sentry.properties (1)
1-5: LGTM! Basic Sentry configuration looks good.
The configuration follows the standard format and includes essential settings. Previous critical issues have been addressed, and the use of environment variables for sensitive data is appropriate.
vite.config.ts (3)
6-6: LGTM!
The Sentry plugin import is correctly placed and follows the established import pattern.
47-47: LGTM!
The source map configuration correctly follows security best practices by enabling source maps only in development.
27-34: Verify Sentry initialization and error handling
Let's verify the complete Sentry integration setup across the codebase.
Also applies to: 47-47
✅ Verification successful
Sentry integration is properly configured with comprehensive error tracking
The Sentry integration is well-implemented with:
- Proper initialization in
main.tswith complete configuration including environment-aware sampling rates, component tracking, and error logging - Correct environment variable setup in
.envand.env.example - Error handling patterns present across simulator components and core application files
- Production-specific error filtering with debug logging in development
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify Sentry initialization and error handling setup
# Check for Sentry initialization in main app file
echo "Checking Sentry initialization..."
rg -l "Sentry.init" src/
# Check for error boundary components
echo "Checking error boundary setup..."
rg -l "errorHandler|captureException|captureMessage" src/
# Check for proper environment variable usage
echo "Checking environment variable usage..."
rg "SENTRY_DSN" .env*
# Verify error tracking in simulator components
echo "Checking simulator error tracking..."
rg "try.*catch.*Sentry" src/simulator/
Length of output: 635
Script:
#!/bin/bash
# Let's check the Sentry initialization code in main.ts and look for error handling patterns
echo "Checking Sentry initialization in main.ts:"
rg -A 5 "Sentry.init" src/main.ts
echo "\nChecking for error handling patterns:"
# Look for try-catch blocks in simulator
rg "try\s*{" src/simulator/ -A 5
# Look for error handling utilities or services
rg -l "error" src/utils/ src/services/
echo "\nChecking for Vue error handlers:"
# Look for Vue error handlers setup
rg "app\.(config|use).*error" src/
rg "errorHandler" src/
echo "\nChecking environment variables usage in code:"
rg "SENTRY_" src/ -g "!*.{json,lock}"
Length of output: 991
Script:
#!/bin/bash
# Let's check for try-catch blocks with fixed regex and explore error handling
echo "Checking for try-catch blocks in simulator:"
rg "try {" src/simulator/ -A 5
echo "\nLooking for error handling patterns:"
# Look for any error-related code in src
rg -l "catch|throw|Error" src/
echo "\nChecking Vue app configuration:"
# Check main.ts for complete setup
cat src/main.ts
echo "\nVerifying Sentry environment configuration:"
# Check if Sentry is properly configured in environment files
cat .env.example
Length of output: 3208
- Add TypeScript type definitions for environment variables - Add validation for required Sentry environment variables - Improve type safety in configuration
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Outside diff range and nitpick comments (2)
src/types/env.d.ts (1)
3-7: Consider improving type safety of the Vue component declaration.The current implementation uses empty object types
{}andanywhich reduces type safety. Consider using more specific types:declare module '*.vue' { import type { DefineComponent } from 'vue' - const component: DefineComponent<{}, {}, any> + const component: DefineComponent<Record<string, unknown>, Record<string, unknown>, unknown> export default component }🧰 Tools
🪛 Biome (1.9.4)
[error] 5-5: Don't use '{}' as a type.
Prefer explicitly define the object shape. '{}' means "any non-nullable value".
(lint/complexity/noBannedTypes)
[error] 5-5: Don't use '{}' as a type.
Prefer explicitly define the object shape. '{}' means "any non-nullable value".
(lint/complexity/noBannedTypes)
vite.config.ts (1)
27-37: Consider enhancing error handling and configurationWhile the basic Sentry configuration is in place, consider adding these improvements for better error tracking:
sentryVitePlugin({ org: "circuitverse", project: "javascript-vue", authToken: process.env.SENTRY_AUTH_TOKEN, + // Add release information for better error tracking + release: process.env.npm_package_version, + // Set error sample rate based on environment + errorSampleRate: process.env.NODE_ENV === 'production' ? 0.5 : 1.0, + // Ignore common browser extensions errors + ignoreErrors: [ + /^chrome-extension:\/\//, + /^moz-extension:\/\// + ], enabled: process.env.NODE_ENV === 'production', telemetry: false, debug: process.env.NODE_ENV === 'development' }),🧰 Tools
🪛 Biome (1.9.4)
[error] 32-32: expected
:but instead foundnewRemove new
(parse)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
src/types/env.d.ts(1 hunks)vite.config.ts(3 hunks)
🧰 Additional context used
🪛 Biome (1.9.4)
src/types/env.d.ts
[error] 5-5: Don't use '{}' as a type.
Prefer explicitly define the object shape. '{}' means "any non-nullable value".
(lint/complexity/noBannedTypes)
[error] 5-5: Don't use '{}' as a type.
Prefer explicitly define the object shape. '{}' means "any non-nullable value".
(lint/complexity/noBannedTypes)
vite.config.ts
[error] 32-32: expected : but instead found new
Remove new
(parse)
🔇 Additional comments (3)
src/types/env.d.ts (2)
14-16: LGTM!
The ImportMeta interface is correctly defined with proper readonly type safety.
18-26: Ensure proper handling of sensitive Sentry tokens.
The SENTRY_AUTH_TOKEN is a sensitive value. Please ensure:
- It's not committed to version control
- It's properly configured in CI/CD secrets
- It's documented in the project's setup guide
vite.config.ts (1)
6-6: LGTM!
The Sentry plugin import is correctly placed and properly formatted.
| interface ImportMetaEnv { | ||
| readonly VITE_SENTRY_DSN: string | ||
| readonly NODE_ENV: 'development' | 'production' | 'test' | ||
| } |
There was a problem hiding this comment.
💡 Codebase verification
Environment variables for Sentry configuration need to be properly utilized
The codebase shows hardcoded Sentry DSN in src/main.ts instead of using the defined VITE_SENTRY_DSN environment variable. Additionally, while SENTRY_AUTH_TOKEN is properly defined for build configuration, the runtime configuration could benefit from additional environment variables for:
tracesSampleRatereplaysSessionSampleRate
These values are currently hardcoded but would be better managed through environment variables for different environments.
src/main.ts: Replace hardcoded DSN withimport.meta.env.VITE_SENTRY_DSNsrc/types/env.d.ts: Consider adding:readonly VITE_SENTRY_TRACES_SAMPLE_RATE?: string readonly VITE_SENTRY_REPLAYS_SAMPLE_RATE?: string
🔗 Analysis chain
Verify completeness of Sentry environment variables.
Consider adding other common Sentry configuration variables that might be needed:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Search for Sentry-related environment variable usage in the codebase
rg -g '!*.d.ts' 'VITE_SENTRY|SENTRY_' --type ts --type vue
# Check .env files for any additional Sentry variables
fd -e .env -x cat {} | grep -i 'sentry'
Length of output: 130
Script:
#!/bin/bash
# Search for Sentry-related environment variable usage with correct file types
rg 'VITE_SENTRY|SENTRY_' --type typescript --type-add 'vue:*.vue'
# Look for any .env files in the repository
fd '.env'
# Look for Sentry configuration or initialization code
rg 'Sentry\.(init|configure)' --type typescript --type-add 'vue:*.vue'
Length of output: 220
Script:
#!/bin/bash
# Search for Sentry-related environment variable usage with simpler approach
rg 'VITE_SENTRY|SENTRY_' -t ts -t tsx
# Look for any .env files in the repository
find . -name ".env*"
# Look for Sentry configuration or initialization code
rg 'Sentry\.(init|configure)' -t ts -t tsx
Length of output: 185
Script:
#!/bin/bash
# Check contents of .env files for Sentry configuration
cat .env.example
# Search for Sentry-related code without file type restrictions
rg 'VITE_SENTRY|SENTRY_'
# Search for Sentry initialization without file type restrictions
rg 'Sentry\.(init|configure)'
Length of output: 672
Script:
#!/bin/bash
# Check Sentry initialization configuration
rg -A 5 'Sentry\.init' src/main.ts
# Look for any other potential Sentry environment variables in the configuration
rg 'Sentry' src/main.ts
Length of output: 392
| ...(!process.env.SENTRY_AUTH_TOKEN || !process.env.SENTRY_DSN) && { | ||
| throw new Error('SENTRY_AUTH_TOKEN and SENTRY_DSN are required for Sentry integration') | ||
| }, |
There was a problem hiding this comment.
Fix the environment variable validation syntax
The current implementation has a syntax error in the spread operator. The error throwing logic needs to be restructured.
Apply this fix:
- ...(!process.env.SENTRY_AUTH_TOKEN || !process.env.SENTRY_DSN) && {
- throw new Error('SENTRY_AUTH_TOKEN and SENTRY_DSN are required for Sentry integration')
- },
+ // Validate environment variables before plugin initialization
+ beforeBuild: () => {
+ if (!process.env.SENTRY_AUTH_TOKEN || !process.env.SENTRY_DSN) {
+ throw new Error('SENTRY_AUTH_TOKEN and SENTRY_DSN are required for Sentry integration');
+ }
+ },📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ...(!process.env.SENTRY_AUTH_TOKEN || !process.env.SENTRY_DSN) && { | |
| throw new Error('SENTRY_AUTH_TOKEN and SENTRY_DSN are required for Sentry integration') | |
| }, | |
| // Validate environment variables before plugin initialization | |
| beforeBuild: () => { | |
| if (!process.env.SENTRY_AUTH_TOKEN || !process.env.SENTRY_DSN) { | |
| throw new Error('SENTRY_AUTH_TOKEN and SENTRY_DSN are required for Sentry integration'); | |
| } | |
| }, |
🧰 Tools
🪛 Biome (1.9.4)
[error] 32-32: expected : but instead found new
Remove new
(parse)
| sentryVitePlugin({ | ||
| org: "circuitverse", | ||
| project: "javascript-vue", | ||
| authToken: process.env.SENTRY_AUTH_TOKEN, | ||
| ...(!process.env.SENTRY_AUTH_TOKEN || !process.env.SENTRY_DSN) && { | ||
| throw new Error('SENTRY_AUTH_TOKEN and SENTRY_DSN are required for Sentry integration') | ||
| }, | ||
| enabled: process.env.NODE_ENV === 'production', | ||
| telemetry: false, | ||
| debug: process.env.NODE_ENV === 'development' | ||
| }), |
There was a problem hiding this comment.
💡 Codebase verification
Sentry integration needs error handling improvements
The Sentry SDK is properly initialized in main.ts, but the implementation is missing crucial error handling components:
- No global error handler is configured for Vue application
- Missing error boundary components for graceful error handling
- No custom error tracking setup for critical user interactions
To improve the integration:
- Add
app.config.errorHandlerinmain.tsto capture unhandled Vue errors - Implement error boundary components for critical UI sections
- Consider adding
errorCapturedhooks in top-level components
🔗 Analysis chain
Verify Sentry integration with the frontend application
The Sentry configuration looks good, but let's verify the integration with the frontend application.
Also applies to: 50-50
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify Sentry integration in the frontend application
# Check for Sentry initialization in main application file
echo "Checking for Sentry initialization..."
rg -l "Sentry.init" src/
# Check for proper error boundaries in Vue components
echo "Checking for error boundary components..."
rg -l "errorCaptured|onErrorCaptured" src/
# Verify Sentry is imported in key application files
echo "Checking Sentry imports..."
rg -l "@sentry/(vue|browser)" src/
Length of output: 371
Script:
#!/bin/bash
# Let's check the actual implementation in main.ts and look for any error boundaries
echo "=== Checking Sentry initialization implementation ==="
rg -A 10 "Sentry.init" src/main.ts
echo -e "\n=== Checking for error boundary components or handlers ==="
# Looking for Vue error handlers with context
rg -A 5 "errorCaptured|onErrorCaptured|errorHandler" src/
echo -e "\n=== Checking app configuration for error handling ==="
# Looking for app-level error configuration
rg -A 5 "app\.(config|use)" src/main.ts
Length of output: 967
🧰 Tools
🪛 Biome (1.9.4)
[error] 32-32: expected : but instead found new
Remove new
(parse)
feat(simulator): integrate Sentry error tracking
Fixes CircuitVerse/CircuitVerse#4962
Describe the changes you have made in this PR -
Integrated Sentry error tracking into the CircuitVerse simulator frontend with real-time error monitoring and analytics:
Current Analytics (Last 53 minutes):
Key Issues Identified and Fixed:
Canvas Context Errors:
TypeError: this.canvas.getContext is not a functionsimulatorvue/src/simulator/src/simulationAreaPlot Area Resize Error:
TypeError: Cannot set properties of null (setting 'width')simulatorvue/src/simulator/src/plotAreaIntegration Verification:
simulatorvue/src/mainImplementation Details:
Summary by CodeRabbit
Release Notes
New Features
Bug Fixes
Documentation
.env.exampleto include new Sentry configuration variables.Chores
sentry.propertiesconfiguration file for Sentry settings.