Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: build with app platform, publish independent services #512

Merged
merged 9 commits into from
May 6, 2020

Conversation

amcgee
Copy link
Member

@amcgee amcgee commented Apr 20, 2020

Requires dhis2/app-platform#368

Closes #370

This migrates all app-service packages to build with DHIS2 App Platform (instead of running pretty much the same steps locally). This also makes all service packages (@dhis2/app-service-config and @dhis2/app-service-data) public and published to npm, so we don't have to worry about bundling them all together and so that types can be properly exposed and consumed by IDEs.

For now type extraction and tsconfig settings remain in this repo, but eventually they should be baked into the platform so that typescript libs always output consistent type declaration files.

@amcgee amcgee requested a review from varl April 20, 2020 11:47
@amcgee amcgee marked this pull request as ready for review April 27, 2020 10:04
Comment on lines +17 to +19
"@dhis2/app-runtime": "file:../../runtime",
"@dhis2/app-service-config": "file:../../services/config",
"@dhis2/app-service-data": "file:../../services/data",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it correct that the peerDeps should be linked to "file:" when "resolutions" is used below?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's the same either way? The dep (not peerDep) could be a version range, but the resolution takes precedence anyway. I think I needed this for the moment since the sup-packages aren't published on npm yet, so it broke when trying to resolve a version range.

Copy link
Member Author

@amcgee amcgee Apr 28, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@varl technically, since there are no "deep" dependencies on @dhis2/app-service-{config|data} the resolutions were superfluous, so I've removed them but the file dep is still required

Copy link
Member Author

@amcgee amcgee May 1, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While technically it works with only dependencies I think the resolutions are more important here (since they're not technically direct dependencies), we can remove the dependency entries once the service packages have been published.

@amcgee amcgee requested a review from varl April 30, 2020 10:10
Copy link
Contributor

@Mohammer5 Mohammer5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@amcgee
Copy link
Member Author

amcgee commented May 1, 2020

Thanks @Mohammer5 !

@amcgee amcgee changed the title refactor: build with app platform, publish independent services feat: build with app platform, publish independent services May 1, 2020
@amcgee amcgee merged commit 70aa726 into master May 6, 2020
@amcgee amcgee deleted the refactor/platform-build branch May 6, 2020 15:33
dhis2-bot added a commit that referenced this pull request May 6, 2020
# [2.2.0](v2.1.2...v2.2.0) (2020-05-06)

### Features

* build with app platform, publish independent services ([#512](#512)) ([70aa726](70aa726))
@dhis2-bot
Copy link
Contributor

🎉 This PR is included in version 2.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

Use app-platform for library build
4 participants