Project: GameDB

This project was created using vscode-remote-try-node and then heavily modified to:

• Make VSCode-specific config optional
• Support multiple roots
• Add Jest testing + debugging
• Remove dependency on yarn
• Add .editorconfig support
• Add Docker-in-Docker support

You can find the original documentation from vscode-remote-try-node below. But, before you try to use these VSCode-specific features, run the ./initvscode.sh script to create the necessary config files.

---

Try Out Development Containers: Node.js

This is a sample project that lets you try out the VS Code Remote - Containers extension in a few easy steps.

Note: If you're following the quick start, you can jump to the Things to try section.

Setting up the development container

Follow these steps to open this sample in a container:

1. If this is your first time using a development container, please follow the getting started steps.

2. To use this repository, you can either open a locally cloned copy of the code:

   • Clone this repository to your local filesystem.
   • Press F1 and select the Remote-Containers: Open Folder in Container... command.
   • Select the cloned copy of this folder, wait for the container to start, and try things out!

   Or open the repository in an isolated Docker volume:

   • Press F1 and select the Remote-Containers: Try a Sample... command.
   • Choose the "Node" sample, wait for the container to start and try things out!

     Note: Under the hood, this will use Remote-Containers: Open Repository in Container... command to clone the source code in a Docker volume instead of the local filesystem.

Things to try

Once you have this sample opened in a container, you'll be able to work with it like you would locally.

Note: This container runs as a non-root user with sudo access by default. Comment out "remoteUser": "node" in .devcontainer/devcontainer.json if you'd prefer to run as root.

Some things to try:

1. Edit:
   • Open server.js
   • Try adding some code and check out the language features. Notice that eslint and the vscode-eslint extension are already installed in the container.
2. Terminal: Press Ctrl+Shift+` and type uname and other Linux commands from the terminal window.
3. Build, Run, and Debug:
   • Open server.js
   • Add a breakpoint (e.g. on line 20).
   • Press F5 to launch the app in the container.
   • Once the breakpoint is hit, try hovering over variables, examining locals, and more.
   • Continue, then open a local browser and go to http://localhost:3000 and note you can connect to the server in the container.
4. Forward another port:
   • Stop debugging and remove the breakpoint.
   • Open server.js
   • Change the server port to 5000. (const PORT = 5000;)
   • Press F5 to launch the app in the container.
   • Press F1 and run the Remote-Containers: Forward Port from Container... command.
   • Select port 5000.
   • Click "Open Browser" in the notification that appears to access the web app on this new port.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

License

Copyright © Microsoft Corporation All rights reserved.
Licensed under the MIT License. See LICENSE in the project root for license information.