This repository is maintained as a monorepo. This means that this repository, instead of containing a single project, contains many projects. If you explore our project structure, you'll see the following:

.
├── packages                #
│   ├── charls-js           # 
│   ├── libjpeg-turbojs     # 
│   └── openjpegjs          #
│
├── ...                     # misc. shared configuration
├── lerna.json              # MonoRepo (Lerna) settings
├── package.json            # Shared devDependencies and commands
└── README.md               # This file

ℹ List of DICOM Transfer syntaxes: https://www.dicomlibrary.com/dicom/transfer-syntax/. More on each transfer syntax, how they differ, and in which situations they excel can be found here: https://www.medicalconnections.co.uk/kb/Transfer-Syntax

Transfer Syntax is the language used in DICOM to describe the DICOM file format and the network transfer methods. 3 main variables are contained in the Transfer Syntax:

• VR: Implicit/Explicit
• Endianism: Little-Endian/BigEndian
• Pixel Data Compression

• * - 1.2.840.10008.1.2.4.50: 8-bit RGB can leverage the browser's built in decoder.

• ** - 1.2.840.10008.1.2.4.[92|93]: Not supported in previous image loaders; OpenJPEG may work with these

• *** - Unlike all other DICOM transfer syntaxes, the deflate transfer syntaxes compress the whole of the DICOM data (tags, lengths, VR etc.) rather than just the pixel data - this is done using the standard “deflate” mechanism as used in gzip etc.) It is therefore most suitable for non-pixel objects such as structured reports, presentation states etc.

• 5: JS Decoder

• 57 & 70: JS Decoder

• 1.2 & 2.1 & 99: JS Decoder

• 2.2: JS Decoder

We are leveraging lerna to version and publish packages. Lerna adds tooling on top of yarn workspaces to enable monorepo functionality. Our lerna configuration/usage is confined to:

• package.json
• lerna.json
• .circleci/config.yml

Pull requests attempt to build and test packages that have been modified (when compared against the main branch). "Semantic commit" messages, and the files included in the commit, help lerna determine how package versions should be updated and what to include in changelogs. Example commit messages include:

• fix(charls-decode): should not break when no config option is provided
• feat(encode): add encode API method
• feat(encode): friendlier API method BREAKING_CHANGE

You can read more about the specific lerna features we're using here:

• lerna run <cmd>: Used in package.json
• lerna version: Used in .circleci/config.yml
• lerna publish: Used in .circleci/config.yml
• "Lerna filter options": Used in package.json (--since main)

You can read more about semantic commit messages here:

• Semantic commits

...