refactor(CxxClasses): Rename WASM to Wasm

Correct naming. BREAKING_CHANGE: WASM renamed to Wasm in C++ classes.
InsightSoftwareConsortium · Jan 22, 2023 · 76447af · 76447af
1 parent d8bca6e
commit 76447af
Show file tree

Hide file tree

Showing 132 changed files with 1,041 additions and 1,037 deletions.
diff --git a/.github/workflows/python-wasm.yml b/.github/workflows/python-wasm.yml
@@ -1,4 +1,4 @@
-name: Python WASM
+name: Python Wasm
 
 on: [push,pull_request]
 

diff --git a/BREAKING_CHANGES.md b/BREAKING_CHANGES.md
@@ -10,6 +10,10 @@ For a log and guide when transitioning from itk.js to itk-wasm,
 please see [the migration
 guide](doc/content/docs/itk_js_to_itk_wasm_migration_guide.md).
 
+## From 1.0.0-b.61 to 1.0.0-b.62
+
+- WASM renamed to Wasm in C++ classes.
+
 ## From 1.0.0-b.51 to 1.0.0-b.52
 
 - The default itkwasm CLI build directory is `emscripten-build` instead of `web-build`.

diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -22,7 +22,7 @@
 * **bindgen:** Add npm badge to readme ([f41fefb](https://github.com/InsightSoftwareConsortium/itk-wasm/commit/f41fefb15dead55d0d05358a3bcde59f217efa9a))
 * **bindgen:** Add vite.config.js ([5928148](https://github.com/InsightSoftwareConsortium/itk-wasm/commit/592814851127be0a361af9927439c408e9ee079b))
 * **bindgen:** Build demo with vite ([718866d](https://github.com/InsightSoftwareConsortium/itk-wasm/commit/718866ddb89684da58652b7dc963000fd85b3405))
-* **bindgen:** Copy WASM modules to dist/pipelines/ ([84de1cd](https://github.com/InsightSoftwareConsortium/itk-wasm/commit/84de1cda7ed6e16d112953bb3f94fd94fe8ed92c))
+* **bindgen:** Copy Wasm modules to dist/pipelines/ ([84de1cd](https://github.com/InsightSoftwareConsortium/itk-wasm/commit/84de1cda7ed6e16d112953bb3f94fd94fe8ed92c))
 * **bindgen:** Generate browser ESM bundle ([9c2a112](https://github.com/InsightSoftwareConsortium/itk-wasm/commit/9c2a112bccb5173d0296e3185cb8bae59e27f3bf))
 * **bindgen:** Generate docsify documentation ([41af4f2](https://github.com/InsightSoftwareConsortium/itk-wasm/commit/41af4f23b612f45b10696f8fd4a74ccdafbc6e95))
 * **bindgen:** Generate Node build configuration ([61f7415](https://github.com/InsightSoftwareConsortium/itk-wasm/commit/61f7415ffd763fc9129c87a4f7125091dcf22a1c))

diff --git a/README.md b/README.md
@@ -4,7 +4,7 @@ itk-wasm
 [![Examples](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/examples.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/examples.yml)
 [![Toolchains](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/toolchains.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/toolchains.yml)
 [![JavaScript,TypeScript](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/javascript-typescript.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/javascript-typescript.yml)
-[![Python WASM](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/python-wasm.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/python-wasm.yml)
+[![Python Wasm](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/python-wasm.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/python-wasm.yml)
 [![C++,Native Python](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/cxx-python.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/cxx-python.yml)
 [![WASI](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/wasi.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/wasi.yml)
 

diff --git a/cypress/e2e/pipeline/runPipeline.cy.ts b/cypress/e2e/pipeline/runPipeline.cy.ts
@@ -18,7 +18,7 @@ describe('runPipeline', () => {
   })
 
 
-  it('fetches WASM files from a custom config URL', () => {
+  it('fetches Wasm files from a custom config URL', () => {
     cy.window().then(async (win) => {
       const itk = win.itk
       const configPropertyPipelinesBaseUrl = 'customPipelinesUrl' 
@@ -32,7 +32,7 @@ describe('runPipeline', () => {
     })
   })
 
-  it('fetches WASM files from a custom pipelineBaseUrl URL', () => {
+  it('fetches Wasm files from a custom pipelineBaseUrl URL', () => {
     cy.window().then(async (win) => {
       const itk = win.itk
       const pipelineBaseUrl = new URL('/pipelines', document.location.origin)
@@ -45,7 +45,7 @@ describe('runPipeline', () => {
     })
   })
 
-  it('fetches WASM files from a custom pipelineBaseUrl string', () => {
+  it('fetches Wasm files from a custom pipelineBaseUrl string', () => {
     cy.window().then(async (win) => {
       const itk = win.itk
       const pipelineBaseUrl = '/pipelines'
@@ -58,7 +58,7 @@ describe('runPipeline', () => {
     })
   })
 
-  it('fetches WASM files from a custom pipelineWorkerUrl string', () => {
+  it('fetches Wasm files from a custom pipelineWorkerUrl string', () => {
     cy.window().then(async (win) => {
       const itk = win.itk
       const pipelineBaseUrl = '/pipelines'

diff --git a/dist/dicom/vite.config.js b/dist/dicom/vite.config.js
@@ -24,7 +24,7 @@ export default defineConfig({
     emptyOutDir: false,
   },
   plugins: [
-    // put lazy loaded JavaScript and WASM bundles in dist directory
+    // put lazy loaded JavaScript and Wasm bundles in dist directory
     copy({
       targets: [
         { src: 'node_modules/itk-wasm/dist/web-workers/bundles/pipeline.worker.js', dest: 'dist/pipelines/web-workers/' },

diff --git a/doc/content/api/browser_io.md b/doc/content/api/browser_io.md
@@ -49,7 +49,7 @@ Read an image from an [ArrayBuffer](https://developer.mozilla.org/en-US/docs/Web
 
 ## readImageHTTP(url: string): Promise<image: [Image](./Image.html)>
 
-Read a server-side generated image created with [`itk::WASMImageIO`](https://github.com/InsightSoftwareConsortium/itk-wasm/blob/main/include/itkWASMImageIO.h). The `url` should point to a directory ending with `.iwi`. Inside the directory, an `index.json` file should be served, along with the pixel and direction buffer file at `${url}/data/data.raw` and `${url}/data/direction.raw`, respectively.
+Read a server-side generated image created with [`itk::WasmImageIO`](https://github.com/InsightSoftwareConsortium/itk-wasm/blob/main/include/itkWasmImageIO.h). The `url` should point to a directory ending with `.iwi`. Inside the directory, an `index.json` file should be served, along with the pixel and direction buffer file at `${url}/data/data.raw` and `${url}/data/direction.raw`, respectively.
 
 ## readImageFileSeries(fileList: File[] | FileList, zSpacing: number = 1.0, zOrigin: number = 0.0, sortedSeries: boolean = false): Promise<{ image: [Image](./Image.html), webWorkerPool: WorkerPool }>
 

diff --git a/doc/content/docs/file_formats.md b/doc/content/docs/file_formats.md
@@ -1,11 +1,11 @@
-title: ITK WASM File Formats
+title: ITK Wasm File Formats
 ---
 
-While IO modules are available to work with a number of [scientific image](./image_formats.html) and [mesh](./mesh_formats.html) file formats, itk-wasm execution pipeline WebAssembly modules only support the ITK WASM File Formats by default. This ensures that size of the WebAssembly pipeline binary is minimal.
+While IO modules are available to work with a number of [scientific image](./image_formats.html) and [mesh](./mesh_formats.html) file formats, itk-wasm execution pipeline WebAssembly modules only support the ITK Wasm File Formats by default. This ensures that size of the WebAssembly pipeline binary is minimal.
 
 The itk-wasm file formats provide performant mapping to the [interface types](./interface_types.html) in a simple JSON + binary array buffer format. The formats can be output in a directory or bundled in a single `.cbor` file.
 
 <dl>
-  <dt><b>ITK WASM Image (.iwi,.iwi.cbor)</b><dt><dd>Serialization of an [Image](../Image.html).</dd>
-  <dt><b>ITK WASM Mesh (.iwm,.iwm.cbor)</b><dt><dd>Serialization of a [Mesh](../Mesh.html), or [PolyData](../PolyData.html).</dd>
+  <dt><b>ITK Wasm Image (.iwi,.iwi.cbor)</b><dt><dd>Serialization of an [Image](../Image.html).</dd>
+  <dt><b>ITK Wasm Mesh (.iwm,.iwm.cbor)</b><dt><dd>Serialization of a [Mesh](../Mesh.html), or [PolyData](../PolyData.html).</dd>
 </dl>
diff --git a/doc/content/docs/index.md b/doc/content/docs/index.md
@@ -1,7 +1,7 @@
 title: Overview
 ---
 
-[![Examples](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/examples.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/examples.yml) [![Toolchains](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/toolchains.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/toolchains.yml) [![JavaScript,TypeScript](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/javascript-typescript.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/javascript-typescript.yml) [![Python WASM](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/python-wasm.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/python-wasm.yml) [![C++,Native Python](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/cxx-python.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/cxx-python.yml) [![WASI](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/wasi.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/wasi.yml)
+[![Examples](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/examples.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/examples.yml) [![Toolchains](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/toolchains.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/toolchains.yml) [![JavaScript,TypeScript](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/javascript-typescript.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/javascript-typescript.yml) [![Python Wasm](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/python-wasm.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/python-wasm.yml) [![C++,Native Python](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/cxx-python.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/cxx-python.yml) [![WASI](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/wasi.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/wasi.yml)
 
 [![npm version](https://badge.fury.io/js/itk-wasm.svg)](https://www.npmjs.com/package/itk-wasm)
 

diff --git a/doc/content/docs/interface_types.md b/doc/content/docs/interface_types.md
@@ -25,7 +25,7 @@ The following [`itk::wasm::Pipeline`](https://github.com/InsightSoftwareConsorti
 
 int main(argc, char * argv[])
 {
-  itk::wasm::Pipeline pipeline("test-pipeline", "A test ITK WASM Pipeline", argc, argv);
+  itk::wasm::Pipeline pipeline("test-pipeline", "A test ITK Wasm Pipeline", argc, argv);
 
   itk::wasm::InputTextStream inputTextStream;
   pipeline.add_option("InputText", inputTextStream, "The input text")->required()->type_name("INPUT_TEXT_STREAM");

diff --git a/doc/content/docs/itk_js_to_itk_wasm_migration_guide.md b/doc/content/docs/itk_js_to_itk_wasm_migration_guide.md
@@ -107,7 +107,7 @@ For compatibility with vtk.js `vtkImageData`, use vtk.js [vtkITKHelper](https://
 
 ## Image file format
 
-The JSON file format is replaced by a WASM file format with a different layout. A directory ending in `.iwi` or a `.iwi.cbor` file is supported for images and a directory ending in `.iwm` and `.iwm.cbor` is supported for meshes and geometry data structures.
+The JSON file format is replaced by a Wasm file format with a different layout. A directory ending in `.iwi` or a `.iwi.cbor` file is supported for images and a directory ending in `.iwm` and `.iwm.cbor` is supported for meshes and geometry data structures.
 
 ## Node Sync functions
 

diff --git a/doc/content/examples/debugging.md b/doc/content/examples/debugging.md
@@ -65,7 +65,7 @@ First, build to WASI WebAssembly with debugging symbols available:
 
 ![WASI debug build](./debugging/wasi-build-debug.png)
 
-Then, the `itk-wasm` CLI can conveniently run the WASM binary with the included WASI runtime:
+Then, the `itk-wasm` CLI can conveniently run the Wasm binary with the included WASI runtime:
 
 ![Run WASI debug](./debugging/run-wasi-debug.png)
 
@@ -126,13 +126,13 @@ Next, enable it in DevTools.
 
   Open DevTools -> Click the *gear (⚙)* icon in the top right corner -> go to the *Experiments* panel -> and tick *WebAssembly Debugging: Enable DWARF support*.
 
-![Enable WASM Debugging](./debugging/enable-chrome-wasm-debugging.png)
+![Enable Wasm Debugging](./debugging/enable-chrome-wasm-debugging.png)
 
 After exitting Settings, you will be prompted to reload DevTools -- reload.
 
 Next, open the options for Chrome WebAssembly Debugging extension:
 
-![WASM Debugging Options](./debugging/devtools-options.png)
+![Wasm Debugging Options](./debugging/devtools-options.png)
 
 Since itk-wasm performs builds in a clean Docker environment, the debugging source paths in the Docker environment are different than the paths on the host system. The debugging extension has a path substitution system that can account for these differences. In the Docker image, the directory where `itk-wasm` is invoked is mounted as `/work`. Substitute `/work` with the directory where the `itk-wasm` CLI is invoked. For example, if `itk-wasm` was invoked at `/home/matt/src/itk-wasm/examples/Debugging`, then:
 

diff --git a/doc/content/examples/hello_pipeline.md b/doc/content/examples/hello_pipeline.md
@@ -3,7 +3,7 @@ title: Hello Pipeline World!
 
 ## Introduction
 
-This example introduces the `itk::wasm::Pipeline`. An `itk::wasm::Pipeline` transforms elegant standalone C++ command line programs into powerful [WebAssembly](https://webassembly.org/) (WASM) modules with a simple, efficient interface for execution in the browser, other programming languages, and on the command line.
+This example introduces the `itk::wasm::Pipeline`. An `itk::wasm::Pipeline` transforms elegant standalone C++ command line programs into powerful [WebAssembly](https://webassembly.org/) (Wasm) modules with a simple, efficient interface for execution in the browser, other programming languages, and on the command line.
 
 Make sure to complete the [Hello World!](./hello_world.html) example before you start your Hello Pipeline adventure.
 
@@ -42,7 +42,7 @@ int main(int argc, char * argv[]) {
 
 The `itk::wasm::Pipeline` extends the most-excellent [CLI11 modern C++ command line parser](https://github.com/CLIUtils/CLI11). In addition to all of CLI11's functionality, `itk::wasm::Pipeline`'s adds:
 
-- Support for execution in WASM modules along with command line execution
+- Support for execution in Wasm modules along with command line execution
 - Support for spatial data structures such as `Image`'s, `Mesh`'s, `PolyData`, and `Transform`'s
 - Support for multiple dimensions and pixel types
 - Colored help output
@@ -152,7 +152,7 @@ npx itk-wasm run hello-pipeline.wasi.wasm -- -- --help
 
 ![Hello pipeline help](./hello_pipeline.png)
 
-The two `--`'s are to separate arguments for the WASM module from arguments to the `itk-wasm` CLI and the WebAssembly interpreter.
+The two `--`'s are to separate arguments for the Wasm module from arguments to the `itk-wasm` CLI and the WebAssembly interpreter.
 
 Try running on an [example image](https://data.kitware.com/api/v1/file/63041ac8f64de9b9501e5a22/download).
 

diff --git a/doc/content/examples/inputs_outputs.md b/doc/content/examples/inputs_outputs.md
@@ -3,7 +3,7 @@ title: Pipeline Inputs and Outputs
 
 ## Introduction
 
-This example dives deeper into `itk::wasm::Pipeline` image inputs and outputs and how they are handled. We will create a pipeline to smooth an image with a median filter, run the WASM from the command line, in Node.js.
+This example dives deeper into `itk::wasm::Pipeline` image inputs and outputs and how they are handled. We will create a pipeline to smooth an image with a median filter, run the Wasm from the command line, in Node.js.
 
 Make sure to complete the [Hello Pipeline!](./hello_pipeline.html) example before you start your filtering journey.
 

diff --git a/doc/content/examples/vite.md b/doc/content/examples/vite.md
@@ -18,7 +18,7 @@ import { viteStaticCopy } from 'vite-plugin-static-copy'
 
 export default defineConfig({
   plugins: [
-    // put lazy loaded JavaScript and WASM bundles in dist directory
+    // put lazy loaded JavaScript and Wasm bundles in dist directory
     viteStaticCopy({
       targets: [
         { src: 'node_modules/itk-wasm/dist/web-workers/*', dest: 'dist/itk/web-workers' },

diff --git a/examples/vite/vite.config.js b/examples/vite/vite.config.js
@@ -6,7 +6,7 @@ const itkConfig = path.resolve(__dirname, 'src', 'itkConfig.js')
 
 export default defineConfig({
   plugins: [
-    // put lazy loaded JavaScript and WASM bundles in dist directory
+    // put lazy loaded JavaScript and Wasm bundles in dist directory
     viteStaticCopy({
       targets: [
         { src: 'node_modules/itk-wasm/dist/web-workers/*', dest: 'dist/itk/web-workers' },

diff --git a/...itkIOComponentEnumFromWASMComponentType.h → ...itkIOComponentEnumFromWasmComponentType.h b/...itkIOComponentEnumFromWASMComponentType.h → ...itkIOComponentEnumFromWasmComponentType.h
@@ -15,8 +15,8 @@
  *  limitations under the License.
  *
  *=========================================================================*/
-#ifndef itkIOComponentEnumFromWASMComponentType_h
-#define itkIOComponentEnumFromWASMComponentType_h
+#ifndef itkIOComponentEnumFromWasmComponentType_h
+#define itkIOComponentEnumFromWasmComponentType_h
 
 #include "itkIOCommon.h"
 #include <string>
@@ -26,7 +26,7 @@ namespace itk
 {
 
 WebAssemblyInterface_EXPORT IOComponentEnum
-IOComponentEnumFromWASMComponentType(const std::string & wasmComponentType);
+IOComponentEnumFromWasmComponentType(const std::string & wasmComponentType);
 
 } // end namespace itk
 #endif
diff --git a/include/itkIOPixelEnumFromWASMPixelType.h → include/itkIOPixelEnumFromWasmPixelType.h b/include/itkIOPixelEnumFromWASMPixelType.h → include/itkIOPixelEnumFromWasmPixelType.h
@@ -15,8 +15,8 @@
  *  limitations under the License.
  *
  *=========================================================================*/
-#ifndef itkIOPixelEnumFromWASMPixelType_h
-#define itkIOPixelEnumFromWASMPixelType_h
+#ifndef itkIOPixelEnumFromWasmPixelType_h
+#define itkIOPixelEnumFromWasmPixelType_h
 
 #include "itkIOCommon.h"
 #include <string>
@@ -26,7 +26,7 @@ namespace itk
 {
 
 WebAssemblyInterface_EXPORT IOPixelEnum
-IOPixelEnumFromWASMPixelType( const std::string & wasmPixelType );
+IOPixelEnumFromWasmPixelType( const std::string & wasmPixelType );
 
 } // end namespace itk
 #endif
diff --git a/include/itkImageToWASMImageFilter.h → include/itkImageToWasmImageFilter.h b/include/itkImageToWASMImageFilter.h → include/itkImageToWasmImageFilter.h
@@ -15,28 +15,28 @@
  *  limitations under the License.
  *
  *=========================================================================*/
-#ifndef itkImageToWASMImageFilter_h
-#define itkImageToWASMImageFilter_h
+#ifndef itkImageToWasmImageFilter_h
+#define itkImageToWasmImageFilter_h
 
 #include "itkProcessObject.h"
-#include "itkWASMImage.h"
+#include "itkWasmImage.h"
 
 namespace itk
 {
 /**
- *\class ImageToWASMImageFilter
- * \brief Convert an Image to an WASMImage object.
+ *\class ImageToWasmImageFilter
+ * \brief Convert an Image to an WasmImage object.
  * 
  * \ingroup WebAssemblyInterface
  */
 template <typename TImage>
-class ITK_TEMPLATE_EXPORT ImageToWASMImageFilter : public ProcessObject
+class ITK_TEMPLATE_EXPORT ImageToWasmImageFilter : public ProcessObject
 {
 public:
-  ITK_DISALLOW_COPY_AND_MOVE(ImageToWASMImageFilter);
+  ITK_DISALLOW_COPY_AND_MOVE(ImageToWasmImageFilter);
 
   /** Standard class type aliases. */
-  using Self = ImageToWASMImageFilter;
+  using Self = ImageToWasmImageFilter;
   using Superclass = ProcessObject;
   using Pointer = SmartPointer<Self>;
   using ConstPointer = SmartPointer<const Self>;
@@ -45,13 +45,13 @@ class ITK_TEMPLATE_EXPORT ImageToWASMImageFilter : public ProcessObject
   itkNewMacro(Self);
 
   /** Run-time type information (and related methods). */
-  itkTypeMacro(ImageToWASMImageFilter, ProcessObject);
+  itkTypeMacro(ImageToWasmImageFilter, ProcessObject);
 
   using DataObjectIdentifierType = Superclass::DataObjectIdentifierType;
   using DataObjectPointerArraySizeType = Superclass::DataObjectPointerArraySizeType;
 
   using ImageType = TImage;
-  using WASMImageType = WASMImage<ImageType>;
+  using WasmImageType = WasmImage<ImageType>;
 
   /** Set/Get the path input of this process object.  */
   using Superclass::SetInput;
@@ -67,17 +67,17 @@ class ITK_TEMPLATE_EXPORT ImageToWASMImageFilter : public ProcessObject
   const ImageType *
   GetInput(unsigned int idx);
 
-  WASMImageType *
+  WasmImageType *
   GetOutput();
-  const WASMImageType *
+  const WasmImageType *
   GetOutput() const;
 
-  WASMImageType *
+  WasmImageType *
   GetOutput(unsigned int idx);
 
 protected:
-  ImageToWASMImageFilter();
-  ~ImageToWASMImageFilter() override = default;
+  ImageToWasmImageFilter();
+  ~ImageToWasmImageFilter() override = default;
 
   ProcessObject::DataObjectPointer
   MakeOutput(ProcessObject::DataObjectPointerArraySizeType idx) override;
@@ -96,7 +96,7 @@ class ITK_TEMPLATE_EXPORT ImageToWASMImageFilter : public ProcessObject
 } // end namespace itk
 
 #ifndef ITK_MANUAL_INSTANTIATION
-#  include "itkImageToWASMImageFilter.hxx"
+#  include "itkImageToWasmImageFilter.hxx"
 #endif
 
 #endif