fix(website): migrate to v2

Author: bugra9

pnpm-lock.yaml

@@ -5,79 +5,106 @@ Usage: cppjs build [options]
 compile the project that was set up using Cpp.js
 
 Options:
-  -p, --platform <platform>  target platform (choices: "All", "WebAssembly", "Android", "iOS", default: "All")
-  -h, --help                 display help for command
+  -p, --platform <platform>      target platform (choices: "wasm", "android", "ios")
+  -a, --arch <arch>              target architecture (choices: "wasm32", "wasm64", "arm64-v8a", "x86_64", "iphoneos", "iphonesimulator")
+  -r, --runtime <runtime>        target runtime (choices: "st", "mt")
+  -b, --build-type <buildType>   target build type (choices: "release", "debug")
+  -e, --runtime-env <runtimeEnv> target runtime environment (choices: "browser", "edge", "node")
+  -h, --help                     display help for command
 ```
 
+Each option accepts a comma-separated list. When an option is omitted, all valid values are selected (except `wasm64`, which is opt-in).
+
 <br />
 
 **Output**
+
+The build outputs platform-specific artifacts under `dist/prebuilt/<platform>-<arch>-<runtime>-<buildType>/`. For each WebAssembly target, the corresponding `.js` and `.wasm` files are also emitted with the runtime environment (browser, edge, node) embedded in the file name.
+
 ```
 ├── dist
-│   ├── mylib.wasm
-│   ├── mylib.browser.js
-│   ├── mylib.node.js
+│   ├── mylib-wasm-wasm32-st-release.browser.js
+│   ├── mylib-wasm-wasm32-st-release.browser.wasm
+│   ├── mylib-wasm-wasm32-st-release.edge.js
+│   ├── mylib-wasm-wasm32-st-release.edge.wasm
+│   ├── mylib-wasm-wasm32-st-release.node.js
+│   ├── mylib-wasm-wasm32-st-release.node.wasm
+│   ├── mylib-wasm-wasm32-mt-release.browser.js
+│   ├── mylib-wasm-wasm32-mt-release.browser.wasm
+│   ├── mylib-wasm-wasm32-mt-release.node.js
+│   ├── mylib-wasm-wasm32-mt-release.node.wasm
 │   └── prebuilt
-│       ├── Android-arm64-v8a
+│       ├── wasm-wasm32-st-release
 │       │   ├── include
 │       │   │   └── ...
 │       │   └── lib
-│       │       └── mylib.so
+│       │       └── libmylib.a
 │       │
-│       ├── Android-x86_64
+│       ├── wasm-wasm32-mt-release
 │       │   ├── include
 │       │   │   └── ...
 │       │   └── lib
-│       │       └── mylib.so
+│       │       └── libmylib.a
 │       │
-│       ├── Emscripten-x86_64
+│       ├── android-arm64-v8a-mt-release
 │       │   ├── include
 │       │   │   └── ...
 │       │   └── lib
-│       │       └── mylib.a
+│       │       └── libmylib.a
 │       │
-│       ├── iOS-iphoneos
+│       ├── android-x86_64-mt-release
 │       │   ├── include
 │       │   │   └── ...
 │       │   └── lib
-│       │       └── mylib.a
+│       │       └── libmylib.a
 │       │
-│       ├── iOS-iphonesimulator
+│       ├── ios-iphoneos-mt-release
 │       │   ├── include
 │       │   │   └── ...
 │       │   └── lib
-│       │       └── mylib.a
+│       │       └── libmylib.a
+│       │
+│       ├── ios-iphonesimulator-mt-release
+│       │   ├── include
+│       │   │   └── ...
+│       │   └── lib
+│       │       └── libmylib.a
 │       │
-│       ├── mylib.xcframework.zip
 │       └── CMakeLists.txt
 |
 └── mylib.xcframework
     ├── ios-arm64_arm64e
     │   ├── Headers
     │   │   └── ...
-    │   └── mylib.a
+    │   └── libmylib.a
     │
-    ├── ios-arm64_arm64e_x86_64-simulator
+    ├── ios-arm64_x86_64-simulator
     │   ├── Headers
     │   │   └── ...
-    │   └── mylib.a
+    │   └── libmylib.a
     │
     └── Info.plist
-
 ```
 
-Here is a minimal example:
+Here is a minimal example that builds only the WebAssembly targets:
 
 ```json title="package.json"
 {
     "name": "cf-worker-example",
     "scripts": {
-       "build": "cppjs build -p WebAssembly"
+       "build": "cppjs build -p wasm"
     }
 }
 ```
 
+A more targeted invocation that limits the architecture, runtime, build type, and runtime environment:
+
+```sh
+cppjs build -p wasm -a wasm32 -r st -b release -e browser,node
+```
+
 :::info 
-**Create library function:** You can access the create library function from [this link](https://github.com/bugra9/cpp.js/blob/main/packages/cpp.js/src/functions/createLib.js).  
-**Create webassembly function:** You can access the create webassembly function from [this link](https://github.com/bugra9/cpp.js/blob/main/packages/cpp.js/src/functions/createWasm.js).  
+**Create library function:** You can access the create library function from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cpp.js/src/actions/createLib.js).  
+**Build WebAssembly function:** You can access the build WebAssembly function from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cpp.js/src/actions/buildWasm.js).  
+**Create XCFramework function:** You can access the create XCFramework function from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cpp.js/src/actions/createXCFramework.js).  
 :::

website/docs/api/cli/build.md

@@ -33,6 +33,6 @@ CMake suite maintained and supported by Kitware (kitware.com/cmake).
 
 :::info
 **Docker Image:** You can access the docker image from [this link](https://hub.docker.com/r/bugra9/cpp.js).  
-**Dockerfile:** You can access the dockerfile from [this link](https://github.com/bugra9/cpp.js/blob/main/packages/cppjs-core-docker/Dockerfile).  
-**Run Function:** You can access the run function from [this link](https://github.com/bugra9/cpp.js/blob/main/packages/cpp.js/src/functions/run.js).
+**Dockerfile:** You can access the dockerfile from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cppjs-core-docker/Dockerfile).  
+**Run Function:** You can access the run function from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cpp.js/src/actions/run.js).
 :::

website/docs/api/cli/docker.md

@@ -18,5 +18,5 @@ Commands:
 <br />
 
 :::info 
-**Binary function:** You can access the binary function from [this link](https://github.com/bugra9/cpp.js/blob/main/packages/cpp.js/src/bin.js).  
+**Binary function:** You can access the binary function from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cpp.js/src/bin.js).  
 :::

website/docs/api/cli/overview.md

@@ -12,7 +12,7 @@ export default {
 };
 ```
 
-The configuration object consists of six sections. These are:
+The configuration object consists of the sections below. These are:
 
 | Attribute    | Description |
 | -            | -           |
@@ -21,10 +21,10 @@ The configuration object consists of six sections. These are:
 | paths        | This object defines paths, such as the project path |
 | ext          | This object specifies file extensions, including those for header files. |
 | export       | This object includes configurations related to lib generation. |
-| platform     | This object includes platform-specific configuration. |
+| targetSpecs  | This array includes target-specific configuration filtered by platform/arch/runtime/buildType. |
 
 <br />
 
 :::tip
-You can find the JavaScript file that generates the configuration [here.](https://github.com/bugra9/cpp.js/blob/main/packages/cpp.js/src/utils/getConfig.js)
+You can find the JavaScript file that generates the configuration [here.](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cpp.js/src/state/loadConfig.js)
 :::

website/docs/api/configuration/overview.md

@@ -1,40 +1,45 @@
-# Platform
-This object includes platform-specific configuration.
+# Target Specs
+This array includes target-specific configuration. Each entry filters by any combination of `platform`, `arch`, `runtime`, `buildType`, and `runtimeEnv`, and applies its `specs` block to every build target that matches the filter. Omit a field to match all of its values.
 
 Here is a minimal example:
 ```js
 export default {
-    platform: {
-        'Emscripten-x86_64': {
-            ignoreLibName: ['charset'],
-        },
-        'Android-arm64-v8a': {
-            data: {
-                'share/proj': 'proj',
+    targetSpecs: [
+        {
+            platform: 'wasm',
+            specs: {
+                ignoreLibName: ['charset'],
             },
-            env: {
-                PROJ_LIB: '_CPPJS_DATA_PATH_/proj',
+        },
+        {
+            platform: 'android',
+            specs: {
+                data: {
+                    'share/proj': 'proj',
+                },
+                env: {
+                    PROJ_LIB: '_CPPJS_DATA_PATH_/proj',
+                },
             },
         },
-    },
+    ],
     paths: {
         config: import.meta.url,
     },
 };
 ```
 
-### Attributes (Platforms)
+### Filter Fields
 
-| Platforms |
-| ---- |
-| Emscripten-x86_64 |
-| Emscripten-x86_64-browser |
-| Emscripten-x86_64-node |
-| Android-arm64-v8a |
-| iOS-iphoneos |
-| iOS-iphonesimulator |
+| Field       | Allowed values |
+| ----------- | -------------- |
+| platform    | `wasm`, `android`, `ios` |
+| arch        | `wasm32`, `wasm64`, `arm64-v8a`, `x86_64`, `iphoneos`, `iphonesimulator` |
+| runtime     | `st`, `mt` |
+| buildType   | `release`, `debug` |
+| runtimeEnv  | `browser`, `edge`, `node` (only meaningful when `platform === 'wasm'`) |
 
-### Sub-Attributes
+### Spec Sub-Attributes
 
 | Name | Type | Description |
 | ---- | ---- | ----------- |
@@ -46,6 +51,6 @@ export default {
 
 :::tip
 Below are examples demonstrating various uses of the configurations.  
-- [**ignoreLibName:** ['charset']](https://www.npmjs.com/package/@cpp.js/package-iconv?activeTab=code)
-- [**data**, **env**](https://www.npmjs.com/package/@cpp.js/package-proj?activeTab=code)
+- [**ignoreLibName:** ['charset']](https://www.npmjs.com/package/@cpp.js/package-iconv-wasm?activeTab=code)
+- [**data**, **env**](https://www.npmjs.com/package/@cpp.js/package-proj-wasm?activeTab=code)
 :::

website/docs/api/configuration/platform.md

@@ -15,7 +15,7 @@ The table below outlines the headings discussed in this section.
 <br />
 
 :::info
-[Embind](https://emscripten.org/docs/porting/connecting_cpp_and_javascript/embind.html) is utilized to bind C++ functions and classes to JavaScript. In WebAssembly, this functionality is provided by Emscripten. In React Native, the binding is achieved through the [@cpp.js/core-embind-jsi](https://github.com/bugra9/cpp.js/tree/main/packages/cppjs-core-embind-jsi) project, which replaces WebAssembly bindings with JavaScript Interface (JSI).
+[Embind](https://emscripten.org/docs/porting/connecting_cpp_and_javascript/embind.html) is utilized to bind C++ functions and classes to JavaScript. In WebAssembly, this functionality is provided by Emscripten. In React Native, the binding is achieved through the [@cpp.js/core-embind-jsi](https://github.com/bugra9/cpp.js/tree/main/cppjs-core/cppjs-core-embind-jsi) project, which replaces WebAssembly bindings with JavaScript Interface (JSI).
 
 The [bugra9/swig](https://github.com/bugra9/swig/tree/add-embind-support) project, a fork of the original [Swig](https://github.com/swig/swig) project adapted to support Embind, is used to create Embind definitions.
 

website/docs/api/cpp-bindings/overview.md

@@ -65,6 +65,6 @@ files.forEach((fileInfo) => {
 <br />
 
 :::info
-**Browser Functions:** You can access the browser functions from [this link](https://github.com/bugra9/cpp.js/blob/main/packages/cpp.js/src/assets/browser.js).  
-**Node.js Functions:** You can access the Node.js functions from [this link](https://github.com/bugra9/cpp.js/blob/main/packages/cpp.js/src/assets/node.js).  
+**Browser Functions:** You can access the browser functions from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cpp.js/src/assets/browser.js).  
+**Node.js Functions:** You can access the Node.js functions from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cpp.js/src/assets/node.js).  
 :::

website/docs/api/javascript/filesystem.md

@@ -26,7 +26,7 @@ Cpp.js includes helper JavaScript functions to handle cross-platform differences
 <br />
 
 :::info
-**Browser Functions:** You can access the browser functions from [this link](https://github.com/bugra9/cpp.js/blob/main/packages/cpp.js/src/assets/browser.js).  
-**Node.js Functions:** You can access the Node.js functions from [this link](https://github.com/bugra9/cpp.js/blob/main/packages/cpp.js/src/assets/node.js).  
-**React Native Functions:** You can access the React Native functions from [this link](https://github.com/bugra9/cpp.js/blob/main/packages/cppjs-core-embind-jsi/js/embind.js).
+**Browser Functions:** You can access the browser functions from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cpp.js/src/assets/browser.js).  
+**Node.js Functions:** You can access the Node.js functions from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cpp.js/src/assets/node.js).  
+**React Native Functions:** You can access the React Native functions from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cppjs-core-embind-jsi/js/embind.js).
 :::

website/docs/api/javascript/overview.md

@@ -17,7 +17,7 @@ const jsArray = Module.toArray(nativeArray);
 <br />
 
 :::info
-**Browser Functions:** You can access the browser functions from [this link](https://github.com/bugra9/cpp.js/blob/main/packages/cpp.js/src/assets/browser.js).  
-**Node.js Functions:** You can access the Node.js functions from [this link](https://github.com/bugra9/cpp.js/blob/main/packages/cpp.js/src/assets/node.js).  
-**React Native Functions:** You can access the React Native functions from [this link](https://github.com/bugra9/cpp.js/blob/main/packages/cppjs-core-embind-jsi/js/embind.js).
+**Browser Functions:** You can access the browser functions from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cpp.js/src/assets/browser.js).  
+**Node.js Functions:** You can access the Node.js functions from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cpp.js/src/assets/node.js).  
+**React Native Functions:** You can access the React Native functions from [this link](https://github.com/bugra9/cpp.js/blob/main/cppjs-core/cppjs-core-embind-jsi/js/embind.js).
 :::