chore: fix devcontainer build failures in github codespaces

[sayantan007pal]

Fix Devcontainer Build Failures in GitHub Codespaces

Summary

Resolved persistent devcontainer build failures caused by disk space exhaustion and broken feature dependencies. The environment is now leaner, faster, and reliable on standard GitHub Codespaces.

The Issue

Developers were unable to start the devcontainer in GitHub Codespaces, encountering two critical errors:

1. Disk Exhaustion

The build failed with write error: no space left on device (specifically when unpacking libtorch). This was caused by the massive mcr.microsoft.com/devcontainers/universal base image (~10GB+) consuming nearly all available storage on standard 32GB Codespaces instances.

2. Broken Dependency

The ghcr.io/marcozac/devcontainer-features/shellcheck feature was unmaintained and referenced a deprecated dependency, causing build interruptions.

The Fix

1. Optimized Base Image

Switched from the heavy universal image to mcr.microsoft.com/devcontainers/javascript-node:1-22-bookworm. This significantly reduces the container's footprint while providing the latest Node.js environment required for the project.

2. Restored Python Support

Explicitly added the ghcr.io/devcontainers/features/python:1 feature to ensure Python tooling remains available (as it was previously inherited from the universal image).

3. Updated ShellCheck

Replaced the broken marcozac feature with the maintained ghcr.io/devcontainers-extra/features/shellcheck:1.

Impact

• Reliability: The container now builds successfully on standard Codespaces without running out of disk space.
• Performance: Faster container startup and rebuild times due to the smaller image size.
• Maintenance: Dependencies are now pointed to maintained sources.

Verification

Verified by rebuilding the container in a fresh Codespace environment. The build completes successfully, and all required languages (Node.js, Python, R, Julia) are installed and accessible.

issue number #7558

[stdlib-bot]

👋 Hi there! 👋

And thank you for opening your first pull request! We will review it shortly. 🏃 💨

Getting Started

• Please read our contributing guidelines if you haven't already.
• For development guidance, refer to the development guide.

Next Steps

1. A project maintainer will approve GitHub Actions workflows for your PR.
2. All CI checks must pass before your submission can be fully reviewed.
3. You'll need to address any failures in linting or unit tests.

Running Tests Locally

You can use make to run any of the CI commands locally from the root directory of the stdlib repository:

# Run tests for all packages in the math namespace:
make test TESTS_FILTER=".*/@stdlib/math/.*"

# Run benchmarks for a specific package:
make benchmark BENCHMARKS_FILTER=".*/@stdlib/math/base/special/sin/.*"

If you haven't heard back from us within two weeks, please ping us by tagging the "reviewers" team in a comment on this PR.

If you have any further questions while waiting for a response, please join our Gitter channel to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

• Contributing Guidelines
• Development Guide
• Gitter channel
• make rules for running examples
• make rules for running unit tests
• make rules for running benchmarks

[stdlib-bot]

Hello! Thank you for your contribution to stdlib.

We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:

1. Please read our contributing guidelines.

2. Update your pull request description to include this checked box:

   - [x] Read, understood, and followed the [contributing guidelines](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md)

This acknowledgment confirms that you've read the guidelines, which include:

• The developer's certificate of origin
• Your agreement to license your contributions under the project's terms

We can't review or accept contributions without this acknowledgment.

Thank you for your understanding and cooperation. We look forward to reviewing your contribution!