Stream: fhirpath.js
Topic: browser
David Hay (Oct 03 2018 at 16:21):
Which js file should I use for browser use? (ie clinFHIR)...
nicola (RIO/SS) (Oct 03 2018 at 19:44):
Now fhirpath.js is a node module and you can build it for browser with webpack (see demo directory for example). I think, we need something like browser build with everything in one file (webpack?) and may be publish it on some CDN. @Paul Lynch ?
nicola (RIO/SS) (Oct 03 2018 at 19:47):
or we can use github releases
Paul Lynch (Oct 03 2018 at 20:03):
I use webpack to build a browser version for our LHC-Forms form renderer. Perhaps it would be easier for people if we included a built, browser-ready file in the GitHub repository-- then they could just download it.
nicola (RIO/SS) (Oct 03 2018 at 20:26):
that's what github releases for https://help.github.com/articles/creating-releases/
nicola (RIO/SS) (Oct 03 2018 at 20:28):
https://docs.travis-ci.com/user/deployment/releases/
Paul Lynch (Oct 03 2018 at 20:35):
@David Hay If you are eager to get started while we sort this out, you can download my browser-ready version at https://lhncbc.github.io/lforms-fhir-app/bower_components/lforms/app/scripts/fhirpath/fhirpath.min.js
David Hay (Oct 03 2018 at 20:41):
Hi Paul - no, happy to wait till you're ready! Thanks anyway...
Paul Lynch (Oct 03 2018 at 20:47):
@nicola (RIO/SS) A GitHub release looks like just a tag plus some associated assets. It looks like in order to have travis upload it the built file as an asset, we first need to add sometime to our build process that will build the file. I've done that for LHC-Forms, so I can add that in and send you a pull request. I am less certain about the Travis part, but one step at at time.
Paul Lynch (Oct 03 2018 at 20:55):
Apparently *.js is not a supported file type for Git Releases. They support .zip, so I guess I will put the .js in to a .zip.
nicola (RIO/SS) (Oct 03 2018 at 20:56):
we have a build for demo - we can reuse it
Last updated: Apr 12 2022 at 19:14 UTC
