This is a log of itk-wasm breaking changes in the 1.0 beta pre-release. We work to limit any breaking changes to when they are needed, provide backwards compatible interfaces when possible, and document breaking changes. However, for long-term improvement of the package, breaking changes are occasionally needed. These changes are noted here.
For a log and guide when transitioning from itk.js to itk-wasm, please see the migration guide.
- apply-presentation-state-to-dicom-image does not take dicom image out flag: was not supported
- apply-presentation-state-to-dicom-image pgm image out flag: always used
- apply-presentation-state-to-dicom-image presentation-state-output flag is prefixed with
no
to disable as a flag - apply-presentation-state-to-dicom-image bitmap-output flag is prefixed with
no
to disable as a flag - apply-presentation-state-to-image presentation-state-file is an argument, as opposed to an optional parameter, since it is required.
- dicom functions access { data: , path: } arguments instead of just .
.
removed from structured-report-to-html arguments for wrapping- readDICOMTags moved to the @itk-wasm/dicom package as readDicomTags, api changed
- readDICOMTagsArrayBuffer removed (use readDicomTags)
- readImageDICOMFileSeries moved to @itk-wasm/dicom package as readImageDicomFileSeries, api changed
- readImageDicomFileSeries does not take casting options -- use castImage
- readImageDICOMFileSeriesArrayBuffer removed (use readImageDicomFileSeries)
- @itk-wasm/dicom node functions that take file arguments use the file path string directly
- Emscripten modules no longer support filesystem-based IO for binary size / performance.
- WASM renamed to Wasm in C++ classes.
- The default itkwasm CLI build directory is
emscripten-build
instead ofweb-build
.
- Image.metadata is now a Map instead of an Object.