Stream: tooling
Topic: NPM Package resolution
Grahame Grieve (Feb 04 2020 at 03:18):
@Martijn Harthoorn does adding support for https://jira.hl7.org/browse/FHIR-25772 in the java tooling imply that we should change the FHIR NPM package spec? @Nick George
Martijn Harthoorn (Feb 04 2020 at 10:24):
We don't mention it explicitly. And our tooling doesn't support it.
Martijn Harthoorn (Feb 04 2020 at 10:35):
Btw, the ticket refers to the "npm spec", but it's actually just the npm docs.
Martijn Harthoorn (Feb 04 2020 at 10:35):
(if you get my point)
Martijn Harthoorn (Feb 04 2020 at 10:38):
My feeling is that -- if people want to rely on the npm client, just go a head and do so. but as a FHIR specification, we should not try to keep up with the npm docs, as they are more of a make-it-up-as-you-go-along than a standard.
Martijn Harthoorn (Feb 04 2020 at 10:40):
The use case of wanting to use it in a private setting that is not meant for publication, by pointing to a package that is not available as a dependency to others, should imho take us to say: let's not allow it on a public FHIR server.
Grahame Grieve (Feb 04 2020 at 12:27):
agree not to allow it on a public server. I just got asked to implement it
Grahame Grieve (Feb 07 2020 at 03:33):
#GF25772 - we decided to allow this but it won't be supported on the ci-build or packages.fhir.org
Grahame Grieve (Apr 16 2020 at 03:44):
@Ward Weistra the package https://packages.simplifier.net/gefyra.sandbox/0.0.2 has 2 copies of package.json in it
Ward Weistra (Apr 16 2020 at 07:16):
Thanks @Grahame Grieve, that's clearly wrong. I'll take up task to prevent that.
Last updated: Apr 12 2022 at 19:14 UTC
