Updated no-conflict and universal-node examples READMEs (#1253)

Author: matux

examples/angular/README.md

@@ -20,7 +20,7 @@ ng serve
 
 Once the server is running, open your browser and navigate to `http://localhost:4200/`. The application will automatically reload whenever you modify any of the source files.
 
-Now, you can test the Rollbar integration by clicking the buttons "Throw an Error" and "Log a Warning". You 
+Now, you can test the Rollbar integration by clicking the buttons "Throw an Error" and "Log a Warning". You
 
 ## Development server - server-side
 
@@ -42,4 +42,4 @@ Now, you can test the Rollbar integration by navigating to the url `http://local
 
 ## Additional Resources
 
-Need help? Rollbar Support can be reached via email at [email protected] 
+Need help? Rollbar Support can be reached via email at [email protected]

examples/no-conflict/README.md

@@ -1,5 +1,37 @@
-- npm install
-- npm start
+# No-Conflict Mode Example
 
-This only uses a server to get around CORS for loading the rollbar library from a local file via the
-snippet.
+This example demonstrates how to use Rollbar's no-conflict mode, which allows multiple instances of Rollbar to coexist on the same page without interfering with each other.
+
+## Use Case
+
+Perfect for:
+- Third-party libraries that include Rollbar internally
+- Widgets or embedded tools that need their own error tracking
+- Avoiding conflicts when multiple teams use Rollbar on the same page
+
+## Setup
+
+```bash
+npm install
+npm run build
+npm start
+```
+
+## How It Works
+
+1. **Main Page** (`test.html`): Uses the standard Rollbar snippet to track errors
+2. **Tool Library** (`tool.js`): Uses `rollbar.noconflict.umd` to create an isolated instance
+3. **Webpack Build**: Bundles the tool with its own Rollbar instance that won't conflict with the page's instance
+
+## Key Features
+
+- Multiple Rollbar instances can run simultaneously
+- Each instance maintains its own configuration and access token
+- No global namespace pollution
+- Ideal for library authors who want to include Rollbar without affecting the host page
+
+## Testing
+
+After starting the server, visit http://localhost:3000 and:
+- Click "Foo" to trigger an error tracked by the main page's Rollbar
+- Click "Tool" to execute code that uses the embedded library's Rollbar

examples/universal-node/README.md

@@ -1,5 +1,51 @@
-- npm install
-- npm run build
-- npm run start
+# Universal Node.js Example
 
-This uses the local version of rollbar in this repository.
+This example demonstrates Rollbar.js in a universal (isomorphic) JavaScript application with both server-side and client-side error tracking.
+
+## Overview
+
+A full-stack example featuring:
+- **Server**: Express.js with server-side rendering
+- **Client**: React application with webpack bundling
+- **Universal**: Same error tracking on both server and client
+
+## Setup
+
+```bash
+npm install
+npm run build
+npm start
+```
+
+## Features
+
+### Server-Side Error Tracking
+- Catches unhandled exceptions in Express routes
+- Tracks errors with request context (user ID, headers, etc.)
+- Demonstrates both error throwing and manual logging
+
+### Client-Side Error Tracking
+- React error boundaries integration
+- Captures browser errors and user interactions
+- Shares configuration between server and client builds
+
+## Routes
+
+- `/` - Main React application
+- `/error` - Triggers a server-side error (demonstrates Express error handling)
+- `/dolog` - Demonstrates manual server-side logging
+- Click "bar" button - Triggers a client-side error
+
+## How It Works
+
+1. **Server** (`server.js`): Initializes Rollbar for Node.js, handles Express errors
+2. **Client** (`app/App.js`): React app that triggers client-side errors
+3. **Webpack**: Bundles client code with Rollbar browser SDK included
+4. **Hot Reload**: Development mode includes webpack hot middleware
+
+## Testing
+
+Visit http://localhost:3000 and:
+- Click the "bar" button to trigger a client-side error
+- Click "Backend error" link to trigger a server-side error
+- Check your Rollbar dashboard to see both errors tracked