-
Notifications
You must be signed in to change notification settings - Fork 44
fix: Use specified dicom-microscopy-viewer load path #313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| REACT_APP_CONFIG='local' | ||
| REACT_APP_CONFIG='preview' |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -27,3 +27,5 @@ public/config/* | |
| npm-debug.log* | ||
| yarn-debug.log* | ||
| yarn-error.log* | ||
|
|
||
| *code-workspace | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -39,7 +39,7 @@ module.exports = { | |
| */ | ||
| alias: { | ||
| 'dicom-microscopy-viewer': | ||
| 'dicom-microscopy-viewer/dist/dynamic-import/dicomMicroscopyViewer.min.js' | ||
| 'dicom-microscopy-viewer/dynamic-import' | ||
| } | ||
| } | ||
| config.plugins.push( | ||
|
|
@@ -48,7 +48,7 @@ module.exports = { | |
| patterns: [ | ||
| { | ||
| from: './node_modules/dicom-microscopy-viewer/dist/dynamic-import', | ||
| to: './static/js' | ||
| to: './' | ||
|
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I can create settings to specify the sub-path for dicom-microscopy-viewer so that this gets the right sub-path. My preference is still to use a dicom-microscopy-viewer sub path, eg |
||
| } | ||
| ] | ||
| }) | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the current way of writing exports in ECMAscript, so I think we should use this setup.