Troubleshooting Build Errors

This guide covers common webpack build errors encountered when using react_on_rails and how to resolve them.

Table of Contents

• Missing Routes File Error
• ProvidePlugin Module Resolution Errors
• Environment Setup Dependencies
• Shakapacker Compatibility Issues
• For Coding Agents

Missing Routes File Error (js-routes gem)

Note: This error only occurs if you're using the optional js-routes gem to access Rails routes in JavaScript.

Error Message

Cannot read properties of undefined (reading 'module')
TypeError: Cannot read properties of undefined (reading 'module')
    at ProvidedDependencyTemplate.apply

Root Cause

This error occurs when:

1. Your webpack config references Rails routes via ProvidePlugin
2. The js-routes gem hasn't generated the JavaScript routes file
3. You're using js-routes integration but missing the generated file

When You Need js-routes

js-routes is optional and typically used when:

• Rails-heavy apps with React components that need to navigate to Rails routes
• Server-side rendered apps mixing Rails and React routing
• Legacy Rails apps migrating ERB views to React
• Apps using Rails routing patterns for RESTful APIs

When You DON'T Need js-routes

Most modern React apps use:

• Client-side routing (React Router) instead of Rails routes
• Hardcoded API endpoints or environment variables
• SPA (Single Page App) architecture with API-only Rails backend

Solution (if using js-routes)

1. Generate JavaScript routes file:

   bundle exec rails js:export

2. Verify the routes file was created:

   ls app/javascript/utils/routes.js

3. Check webpack configuration includes ProvidePlugin:

   new webpack.ProvidePlugin({
     Routes: '$app/utils/routes',
   });

Alternative Solution (if NOT using js-routes)

Remove the Routes ProvidePlugin from your webpack configuration:

// Remove this line if you don't use js-routes
new webpack.ProvidePlugin({
  Routes: '$app/utils/routes', // ← Remove this
});

ProvidePlugin Module Resolution Errors

Common Error Patterns

• Cannot read properties of undefined (reading 'module')
• Module not found: Error: Can't resolve 'module_name'
• ERROR in ./path/to/file.js: Cannot find name 'GlobalVariable'

Debugging Steps

1. Check file existence:

   find app/javascript -name "routes.*" -type f
   find app/javascript -name "*global*" -type f

2. Verify webpack aliases:

   // In your webpack config
   console.log('Webpack aliases:', config.resolve.alias);

3. Test module resolution:

   # Run webpack with debug output
   bin/shakapacker --debug-shakapacker

4. Check for circular dependencies:

   # Install circular dependency plugin
   npm install --save-dev circular-dependency-plugin

Common Fixes

1. Missing global modules: Ensure all modules referenced in ProvidePlugin exist
2. Incorrect paths: Verify alias paths are correct relative to project root
3. File extensions: Make sure webpack can resolve the file extension

Environment Setup Dependencies

Rails Environment Required

Some operations require a working Rails environment:

• rails js:export (generates routes - only needed if using js-routes gem)
• Asset precompilation
• Server-side rendering

Common Issues

1. Database Connection Errors:

   MONGODB | Error checking localhost:27017: Connection refused

   Solution: These are usually warnings and don't prevent operation. To silence:

   # Run with minimal environment
   RAILS_ENV=development bundle exec rails js:export

2. Missing Dependencies:

   sidekiq-pro is not installed

   Solution: This is typically a warning for optional gems and won't affect builds.

Workarounds

1. Skip database initialization:

   DATABASE_URL=sqlite3:tmp/db.sqlite3 rails js:export

2. Use test environment:

   RAILS_ENV=test rails js:export

Shakapacker Compatibility Issues

Version Compatibility Matrix

Common Upgrade Issues

1. Webpacker to Shakapacker migration incomplete:

   # Remove webpacker references
   grep -r "webpacker" config/

2. Old webpack configuration:

   # Check for deprecated webpack configs
   find config/webpack -name "*.js" -exec grep -l "webpacker" {} \;

Migration Steps

1. Follow the Shakapacker upgrade guide
2. Update webpack configurations
3. Regenerate configurations with rails generate react_on_rails:install

For Coding Agents

Automated Diagnostics

When encountering build errors, run this diagnostic script:

#!/bin/bash
echo "=== React on Rails Build Diagnostics ==="

echo "1. Checking versions..."
bundle show react_on_rails | grep "react_on_rails"
npm list react-on-rails 2>/dev/null | grep "react-on-rails"

echo "2. Checking required files..."
[ -f "app/javascript/utils/routes.js" ] && echo "✓ Routes file exists" || echo "✗ Routes file missing - run 'rails js:export'"

echo "3. Checking webpack config..."
grep -q "ProvidePlugin" config/webpack/*.js && echo "✓ ProvidePlugin found" || echo "✗ ProvidePlugin not found"

echo "4. Checking aliases..."
grep -q "\$app" config/webpack/*.js && echo "✓ App alias found" || echo "✗ App alias missing"

echo "5. Testing build..."
npm run build 2>&1 | head -20

Quick Fixes Checklist

For agents encountering build errors:

1. ✅ Generate routes: rails js:export
2. ✅ Check file existence: Verify all ProvidePlugin modules exist
3. ✅ Update dependencies: bundle update react_on_rails && npm install
4. ✅ Clear cache: rm -rf tmp/cache node_modules/.cache
5. ✅ Regenerate config: rails generate react_on_rails:install (review before applying)

Error Pattern Recognition

Common error patterns for automated detection:

# Missing routes file
/Cannot read properties of undefined.*reading 'module'/

# ProvidePlugin issues
/Error: Can't resolve.*\$app/

# Version compatibility
/webpack.*incompatible/

# Missing dependencies
/Module not found.*react-on-rails/

Automated Solutions

# Auto-fix missing routes
if ! [ -f "app/javascript/utils/routes.js" ]; then
  echo "Generating missing routes file..."
  bundle exec rails js:export
fi

# Auto-fix dependency issues
if grep -q "Cannot read properties" build.log; then
  echo "Updating dependencies..."
  bundle update react_on_rails
  npm install
fi

Need More Help?

• Check the general troubleshooting guide
• Review webpack configuration docs
• Contact [email protected] for professional support