Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Atlas 2.6 - timeouts retrieving JavaScript dependencies
See original GitHub issueKnown bug with ATLAS 2.6
We’ve experienced issues when ATLAS 2.6 loads that not all JavaScript modules are properly downloaded from content delivery networks (CDNs). In particular, this problem was noted for resources loaded off of the UNPKG CDN (https://unpkg.com/). This issue will describe a work-around that you can use to address the problem since we’ve also discovered that the build mechanism that was introduced in ATLAS 2.5 to download and bundle all JavaScript dependencies is not properly functioning in ATLAS 2.6 but has been fixed for the planned ATLAS 2.7 release.
Work-around steps
Clone the ATLAS repository from the current master branch (do not do this in a location where you are currently hosting ATLAS on a web server). Once downloaded, open an NPM command line in the ATLAS root directory and run:
npm run build
This will retrieve all of the JavaScript dependencies required for 2.6 and put them into a folder called node_modules. Copy these to the root of your ATLAS 2.6 folder where you have ATLAS on a web server.
Next, modify the paths section of js/settings.js file to replace the CDN references to the node_modules folder. Here is an example:
Before
"ohdsi-api": "https://unpkg.com/@ohdsi/ui-toolbox@1.0.2/lib/umd/api/index"
After
"ohdsi-api": "../node_modules/@ohdsi/ui-toolbox/lib/umd/api/index"
Refresh your browser and confirm that the JavaScript modules now load properly and double-check your paths to ensure you are pointed to the proper location in the node_modules folder.
Please leave any questions/clarifications/issues on this thread. Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for noting this @anthonysena. I was just debugging this. This is an issue that has been causing us significant grief on several deployments here for a few days now 😃
Closing this out since the 2.7 release fixes this issue and deployments of Atlas 2.7 should use
npm run buildas referenced in the release notes here: https://github.com/OHDSI/Atlas/releases/tag/v2.7.0