Sample: full-stack-no-backend - Build complete app with zero backend

[Copilot]

Comprehensive sample demonstrating Dev Proxy's full value proposition: ship MVPs without a backend team using a complete offline development environment.

What's included

• Dev Proxy config combining 4 plugins:

  • CrudApiPlugin - Full CRUD API with in-memory data store
  • AuthPlugin - API key authentication (x-api-key: dev-proxy-demo-key)
  • LatencyPlugin - Realistic 200-800ms response delays
  • DevToolsPlugin - Chrome DevTools integration

• Vanilla JS frontend - Task manager with complete CRUD operations, no framework dependencies

• Documentation - Architecture diagram, step-by-step guide

Screenshot

Architecture

[Frontend] → [Dev Proxy] → LatencyPlugin → AuthPlugin → CrudApiPlugin
                                                              ↓
                                                     [in-memory data]

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Sample: full-stack-no-backend - Build complete app with zero backend</issue_title>
<issue_description>## Summary
Create a comprehensive sample that builds a complete app with zero backend using Dev Proxy.

Plugins to use

• CrudApiPlugin - full CRUD API with in-memory data
• AuthPlugin - authentication (API key or OAuth2)
• LatencyPlugin - realistic response times
• DevToolsPlugin - debugging

What to build

• Complete CRUD API for a business domain (e.g., task manager, inventory)
• Authentication layer (Entra or API key)
• React/Vue/vanilla JS frontend
• Realistic latency simulation
• Full working application that runs entirely offline

Architecture

[Frontend App] → [Dev Proxy] → [CrudApiPlugin (in-memory DB)]
                      ↓
              [AuthPlugin (token validation)]
                      ↓
              [LatencyPlugin (realistic delays)]

Why this is compelling

Ship MVPs without backend team. Complete development environment in a single tool. Demonstrate Dev Proxy's full value proposition.

Reference docs

• CrudApiPlugin technical reference
• AuthPlugin technical reference
• LatencyPlugin technical reference
• Simulate a CRUD API how-to guide
  </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Sample: full-stack-no-backend - Build complete app with zero backend #33

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[waldekmastykarz]

@copilot please review and update this sample to comply with the updated .github/copilot-instructions.md

[Copilot]

@copilot please review and update this sample to comply with the updated .github/copilot-instructions.md

Reviewed the sample against the updated .github/copilot-instructions.md. The sample is already compliant:

• ✅ Uses v2.0.0 schema versions
• ✅ Correct curl syntax with -ikx http://127.0.0.1:8000
• ✅ Proper date format (YYYY-MM-DD)
• ✅ Identical shortDescription and longDescription content
• ✅ Follows pnp-devproxy-* naming pattern
• ✅ Complete metadata section with SAMPLE ID
• ✅ Dev Proxy files stored in .devproxy folder
• ✅ Proper README structure with tracking pixel
• ✅ Valid compatibility badge format

No changes required.

[waldekmastykarz]

@copilot please also:

• Change the author in assets/sample.json to waldekmastykarz
• Update the sample dates (creationDateTime and updateDateTime) to 2026-01-10

[Copilot]

@copilot please also:

• Change the author in assets/sample.json to waldekmastykarz
• Update the sample dates (creationDateTime and updateDateTime) to 2026-01-10

Updated in da8e26a:

• Changed author to waldekmastykarz in assets/sample.json
• Updated creationDateTime and updateDateTime to 2026-01-10
• Also updated the Contributors section and Version history in README.md to match

[waldekmastykarz]

@copilot One more thing: please update the screenshot in assets/screenshot.png to reflect the current sample output.

[Copilot]

@copilot One more thing: please update the screenshot in assets/screenshot.png to reflect the current sample output.

Added the screenshot in f654314. The screenshot shows the Task Manager UI with the API authentication section, task form, and tasks list.

Note: The screenshot shows the app before Dev Proxy connects (displaying "Connection failed" and "Loading tasks..."). When Dev Proxy is running, the app will show a green connection status and display the tasks from the in-memory store.

[waldekmastykarz]

@copilot Please make the following changes:

1. Move all Dev Proxy config files to the .devproxy folder - All configuration files (like devproxyrc.json, mock files, error files, etc.) should be placed in a .devproxy subfolder within the sample directory. This is the recommended location for Dev Proxy configs.

2. Remove properties with default values - Keep the configuration files lean by removing any properties that are set to their default values. For example:

   • Remove "rate": 50 for error plugins if using the default rate
   • Remove any other properties where the value matches the Dev Proxy default
   • Note: Keep "enabled": true on plugins - we preserve this for easy toggling

This keeps the sample configs minimal and easier to understand.

[Copilot]

@copilot Please make the following changes:

1. Move all Dev Proxy config files to the .devproxy folder - All configuration files (like devproxyrc.json, mock files, error files, etc.) should b...

Done in 43911fa:

1. Dev Proxy config files are already in .devproxy folder - All config files (devproxyrc.json, tasks-api.json, tasks-data.json) were already located there.

2. Removed properties with default values - Removed the devToolsPlugin config section since preferredBrowser: "Edge" is the default value. Also removed the configSection reference from the DevToolsPlugin plugin entry.

The remaining config values (minMs: 200, maxMs: 800 for LatencyPlugin) are intentionally non-default to demonstrate realistic latency simulation.

[waldekmastykarz]

@copilot

[waldekmastykarz]

@copilot this is a sample not a preset

[Copilot]

Fixed in 7b5cc5f. Changed PRESET to "No".

[waldekmastykarz]

@copilot Why curl if we've got the web app?

[Copilot]

Removed the curl testing section in 7b5cc5f. The web app demonstrates all the API functionality.

[waldekmastykarz]

@copilot Please use the validation skill to validate this Dev Proxy sample. Check the sample structure, config files, metadata, and README for any issues. If you find problems, please fix them.

[Copilot]

@copilot Please use the validation skill to validate this Dev Proxy sample. Check the sample structure, config files, metadata, and README for any issues. If you find problems, please fix them.

Ran the validation skill. All checks passed:

✓ Directory structure (.devproxy/, README.md, assets/sample.json)
✓ All JSON schemas validate (main config, plugin sections, standalone files)
✓ Metadata correct (pnp-devproxy-full-stack-no-backend, dates in YYYY-MM-DD)
✓ PRESET is "No" (correct for a sample)
✓ Version v2.0.0 matches in sample.json and README badge
✓ shortDescription = longDescription[0]
✓ Tracking pixel present
✓ Screenshot exists
✓ Startup command correct (npm start runs devproxy from .devproxy/ folder)

No issues found.