consolidate examples and fixtures (#89)

* Add websocket example and tests

* consolidate examples and tests

Author: emily-shen

.github/workflows/tests.yml

@@ -22,17 +22,7 @@ jobs:
           cache: 'npm'
 
       - name: Install dependencies and run tests for all fixtures
-        run: |
-          for fixture in fixtures/*/; do
-            if [ -f "$fixture/package.json" ]; then
-              echo "Installing dependencies for $fixture"
-              cd "$fixture"
-              npm install
-              echo "Running tests for $fixture"
-              npm run test
-              cd - > /dev/null
-            fi
-          done
+        run: npm run test
         timeout-minutes: 10
 
 
@@ -54,7 +44,7 @@ jobs:
 
       - name: Type check all fixtures
         run: |
-          for fixture in fixtures/*/; do
+          for fixture in examples/*/; do
             if [ -f "$fixture/tsconfig.json" ]; then
               echo "Type checking $fixture"
               cd "$fixture"

CONTRIBUTING.md

@@ -5,5 +5,6 @@ Thanks for being interested in contributing to @cloudflare/containers!
 ## Developing
 
 1. Clone the repo and install dependencies with `npm i`
-2. The code for the Container class is in `src/lib`, primarily in `container.ts`. You can use the examples in `example` or `example-node` to test your changes, either locally by running `npx wrangler dev`, which will automatically pick up changes to `src/lib`, or by deploying your container with `npx wrangler deploy`.
-3. If your PR will make user-impacting changes, you can add a `patch` changeset by running `npx changesets@cli`. This will ensure your change is included in our changelog.
+2. The code for the Container class is in `src/lib`, primarily in `container.ts`. You can use `examples` to test your changes, either locally by running `npx wrangler dev`, which will automatically pick up changes to `src/lib`, or by deploying your container with `npx wrangler deploy`.
+3. Add tests (located in `examples`) and run tests with `npm run test`.
+4. If your PR will make user-impacting changes, you can add a `patch` changeset by running `npx changesets@cli`. This will ensure your change is included in our changelog.