Our custom OHIF Viewer.
Go to file
2019-07-15 13:03:29 -04:00
.circleci ci(rollbar): Add Rollbar script during CI deploy 2019-06-27 09:41:21 +02:00
.vscode Add dotenv syntax highlighting to list of recommended extensions 2019-04-29 12:58:34 -04:00
extensions Fix ESM symlink build for Viewers 2019-07-15 13:03:29 -04:00
platform Fix ESM symlink build for Viewers 2019-07-15 13:03:29 -04:00
.eslintrc Commit changes before a long weekend 2019-07-05 22:58:25 -04:00
.gitignore ci: add e2e tests with cypress 2019-06-22 10:02:07 -04:00
.prettierrc Move @babel dependencies up to workspace root 2019-07-04 20:35:30 -04:00
aliases.config.js Begin updating dependent libraries to use sync'd webpack builds w/ watches 2019-07-05 13:28:49 -04:00
babel.config.js Begin updating dependent libraries to use sync'd webpack builds w/ watches 2019-07-05 13:28:49 -04:00
eslintAliasesResolver.js Begin updating dependent libraries to use sync'd webpack builds w/ watches 2019-07-05 13:28:49 -04:00
lerna.json Better entrypoint for extensions 2019-07-09 12:56:08 -04:00
package.json Fix ESM symlink build for Viewers 2019-07-15 13:03:29 -04:00
README.md Push changes up to switch PCs 2019-07-11 13:12:37 -04:00
yarn.lock Begin updating dependent libraries to use sync'd webpack builds w/ watches 2019-07-05 13:28:49 -04:00

OHIF Medical Imaging Platform

# Flip workspaces flag
yarn config set workspaces-experimental true

# Force install
yarn install --force

# Link
# Redundent with yarn workspaces
npx lerna bootstrap
# Link for local dev
cd ./extensions/my-package
npx lerna add @ohif/my-package --scope=@ohif/my-package-consumer
# Add shared dev dependency for workspace
yarn add --dev -W package-name

// module vs main vs jsnext:main vs browser https://babeljs.io/blog/2018/06/26/on-consuming-and-publishing-es2015+-packages

Webpack: https://webpack.js.org/configuration/resolve/

UMD builds go through

  • index.umd.js
  • Extensions passed in via window config

PWA builds go through

  • index.js
  • Extensions specified in file or by window config

The module property should point to a script that utilizes ES2015 module syntax but no other syntax features that aren't yet supported by browsers or node. This enables webpack to parse the module syntax itself, allowing for lighter bundles via tree shaking if users are only consuming certain parts of the library.