ES6 Imports

Hello! This is Abby from Symptomatic and the Clinical Meteor project. I think we connected a few months back at the Baltimore Working Group and Application Roundtable.

Quick question: what do you all think about refactoring to use ES6 import statements? Have you given this much thought?

I ask because there’s some conversation from the FHIR-I group and others about identifying an NPM client library to rally some effort around. Most every client we’ve been tracking is a mix of some features in some areas, and not in others. But fhir-kit-clients seems to have decent multi-version support, ES6 classes, and test coverage. Seems like it might be an easier lift to add ES6 imports rather than adding multi-version support or dropping dependencies from the other libraries.

I ask about imports in particular, since they provide the same functionality as require statements, but optimized by the V8 interpreter, and therefore accessible on both server and client.

If we could refactor to ES6 imports, I would likely add support for it in the Meteor on FHIR project.

Thanks!

[bkaney]

Okay, I am going to close this issue. If you have problems, feel free to open a new ticket. thanks!

[bkaney]

With 1.4.0 release we paved the way for the library to work better on the client side. Here are a few examples: https://github.com/Vermonster/fhir-kit-client-examples

We still can work on converting to ESM, but perhaps the 1.4.0 release will work in your MeteorJS out-of-the-box?