fix(build): add path-with-spaces check and document ARM64 dev container support

Add early failure when project directory path contains spaces, as GNU make
and shell scripts fail in such environments. Update documentation to state
that the dev container now supports ARM64/Apple Silicon architectures.
Add required usage/examples sections to FAQ and setting_up_a_devcontainer
to satisfy markdown linter. Fix devcontainer-setup link in FAQ.

Author: shiavm006

.devcontainer/README.md

@@ -30,7 +30,7 @@ limitations under the License.
 
 <section class="intro">
 
-This folder includes configuration for developing the project in a local container or using [GitHub Codespaces][github-codespaces].
+This folder includes configuration for developing the project in a local container or using [GitHub Codespaces][github-codespaces]. The dev container supports both x86_64 and ARM64 (Apple Silicon) architectures.
 
 </section>
 
@@ -44,6 +44,14 @@ This folder includes configuration for developing the project in a local contain
 
 <!-- /.usage -->
 
+<!-- Section to include examples. Make sure to keep an empty line after the `section` element and another before the `/section` close. -->
+
+<section class="examples">
+
+</section>
+
+<!-- /.examples -->
+
 <!-- Section to include usage notes. Make sure to keep an empty line after the `section` element and another before the `/section` close. -->
 
 <section class="notes">

Makefile

@@ -30,6 +30,15 @@ this_dir := $(patsubst %/,%,$(this_dir))
 # Define the root project directory:
 ROOT_DIR ?= $(this_dir)
 
+# Check for spaces in the project path.
+# GNU make and the installation process fail when the path contains spaces.
+# See CONTRIBUTING.md and docs/contributing/development.md for details.
+_empty :=
+_space := $(_empty) $(_empty)
+ifneq ($(findstring $(_space),$(ROOT_DIR)),)
+$(error The project directory path contains spaces. GNU make and the installation process will fail. Please clone the repository to a path without spaces (e.g., use stdlib_gsoc instead of stdlib gsoc). See CONTRIBUTING.md and docs/contributing/development.md for details.)
+endif
+
 # Define the top-level directory containing source files:
 SRC_DIR ?= $(ROOT_DIR)/lib/node_modules
 

docs/contributing/FAQ.md

@@ -64,7 +64,7 @@ There are primarily two options for setting up your development environment to c
 1. [Manually setting up the development environment][manual-setup]
 2. [Setting up the dev container][devcontainer-setup]
 
-Note: The dev container does not yet support ARM64 architectures. For more information, or if you're interested in adding ARM64 support, you can visit this [issue][devcontainer-issue].
+Note: The dev container supports ARM64/Apple Silicon. The base Node.js development environment works on both x86_64 and ARM64 architectures. Some optional features (e.g., R, Julia) may have architecture-specific limitations. For issues or feedback, see this [issue][devcontainer-issue].
 
 <a name="install-cppcheck"></a>
 
@@ -381,6 +381,20 @@ For more `make` commands, refer to the [documentation][benchmark] on running ben
 - [Git Cheatsheet][git-guide]
 - [Other make commands][make-commands]
 
+<!-- FIXME: the following two empty sections are merely to satisfy the linter for `expected-html-sections` which cannot, atm, be turned off -->
+
+<section class="usage">
+
+</section>
+
+<!-- /.usage -->
+
+<section class="examples">
+
+</section>
+
+<!-- /.examples -->
+
 <section class="links">
 
 [git]: http://git-scm.com/
@@ -401,7 +415,7 @@ For more `make` commands, refer to the [documentation][benchmark] on running ben
 
 [manual-setup]: https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md#step-0-github
 
-[devcontainer-setup]: https://github.com/stdlib-js/stdlib/blob/87cbd67623892f90ddeea94e1d4e01eeada417b5/docs/devcontainer_setup.md
+[devcontainer-setup]: https://github.com/stdlib-js/stdlib/blob/develop/docs/contributing/setting_up_a_devcontainer.md
 
 [devcontainer-issue]: https://github.com/stdlib-js/stdlib/issues/4934
 

docs/contributing/setting_up_a_devcontainer.md

@@ -30,7 +30,7 @@ Dev containers are Docker containers that are specifically configured to provide
 
 The stdlib repository includes a preconfigured dev container, making it the easiest way to set up your development environment. It ensures proper linting, EditorConfig, and tooling are configured right from the start.
 
-**Note:** The dev container does not yet support ARM64 architectures. For more information, or if you're interested in adding ARM64 support, you can visit this [issue][devcontainer-issue].
+**Note:** The dev container supports ARM64/Apple Silicon. The base Node.js development environment works on both x86_64 and ARM64 architectures. Some optional features (e.g., R, Julia) may have architecture-specific limitations. For issues or feedback, see this [issue][devcontainer-issue].
 
 ### Prerequisites
 
@@ -113,6 +113,20 @@ If you see this when you open the terminal, then the dev container installation
     <br>
 </div>
 
+<!-- FIXME: the following two empty sections are merely to satisfy the linter for `expected-html-sections` which cannot, atm, be turned off -->
+
+<section class="usage">
+
+</section>
+
+<!-- /.usage -->
+
+<section class="examples">
+
+</section>
+
+<!-- /.examples -->
+
 <section class="links">
 
 [git]: http://git-scm.com/