Skip to content

Commit ec7691f

Browse files
committed
fix: updating container README form using yarn to pnpm
1 parent 3c46232 commit ec7691f

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

.devcontainer/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The container uses a conservative caching approach to prevent cache corruption i
3333
- Python packages: `/home/vscode/.cache/pip`
3434

3535
3. **Intentionally Not Cached**: These tools use their default cache locations to avoid contamination
36-
- NPM, Yarn (different dependency versions per branch)
36+
- NPM (different dependency versions per branch)
3737
- Foundry, Solidity (different compilation artifacts per branch)
3838
- Hardhat (different build artifacts per branch)
3939

@@ -49,7 +49,7 @@ To start the dev container:
4949

5050
When the container starts, the `project-setup.sh` script will automatically run and:
5151

52-
- Install project dependencies using yarn
52+
- Install project dependencies using pnpm
5353
- Configure Git to use SSH signing with your forwarded SSH key
5454
- Source shell customizations if available in PATH
5555

@@ -79,8 +79,8 @@ These environment variables are needed for Git commit signing to work properly.
7979
If you encounter build or compilation issues that seem related to cached artifacts:
8080

8181
1. **Rebuild the container**: This will start with fresh local caches
82-
2. **Clean project caches**: Run `yarn clean` to clear project-specific build artifacts
83-
3. **Clear node modules**: Delete `node_modules` and run `yarn install` again
82+
2. **Clean project caches**: Run `pnpm clean` to clear project-specific build artifacts
83+
3. **Clear node modules**: Delete `node_modules` and run `pnpm install` again
8484

8585
### Git SSH Signing Issues
8686

0 commit comments

Comments
 (0)