Stream: IG creation
Topic: Populating package.json url
Elliot Silver (Jan 10 2022 at 22:10):
Looking at the FHIR NPM Package Specification it references a url element, that matches ImplementationGuide.manifest.rendering. At what point in the publication process does this get populated in the IG resource and package.json, because I don't see it in my local build output, or in Registry packages? Or is this a manual step?
Grahame Grieve (Jan 10 2022 at 22:32):
which isn't populated?
John Moehrke (Jan 10 2022 at 22:33):
likely that last magical invocation of the builder... possibly the -publish-update or the -go-publish... no idea what the difference is
Elliot Silver (Jan 10 2022 at 22:55):
Grahame Grieve said:
which isn't populated?
Either ImplementationGuilde.manifest.rendering or package.json's url element in the output of IG publisher, and on the project I'm working on that's been pushed to the registry by Simplifier.
Grahame Grieve (Jan 10 2022 at 23:57):
I can't speak to what Simplifier does but I thought I was populating package.json/url
Elliot Silver (Jan 10 2022 at 23:58):
Is it something that should be done as part of the publication process, or just the build?
Grahame Grieve (Jan 10 2022 at 23:59):
normal build. I don't think that the publication process ever changes the package
Ward Weistra (Jan 11 2022 at 16:25):
@Elliot Silver For publishing via Simplifier.net you could just update that URL in your project's package.json before you publish a package. It should then make it to the package.json in your resulting package.
Last updated: Apr 12 2022 at 19:14 UTC
