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

Fix issue where HOSTS_VERSION was incompatible with packages not using webpack #142

Merged
merged 1 commit into from
Oct 25, 2022

Conversation

prestomation
Copy link
Contributor

We were setting the HOSTS_VERSION at build time using webpack.

We also want customers who want to use modules/not use our webpack build to be able to do so.

These are incompatible.

To solve this, we are now writing out the version number into source at release time. This should have the same effect as before, anyone using an NPM release will get a version number, otherwise you will have 'development'.

I tested this in a release in my fork, you can see the overwritten file here in the artifacts: https://github.com/prestomation/amazon-sumerian-hosts/actions/runs/3301290701

Related Issue #133

Reviewer Testing Instructions

Can't completely test without creating a release.
After this is merged we will perform a release and test our repro cases to fully test

Submission Checklist

I confirm that I have...

  • [ x] removed hard-coded Cognito IDs
  • [ x] manually smoke-tested the BabylonJS integration tests
  • [ x] manually smoke-tested the BabylonJS demos
  • [ x] manually smoke-tested the Three.js integration tests
  • [ x] manually smoke-tested the Three.js demo

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

…g webpack.

We were setting the HOSTS_VERSION at build time using webpack.

We also want customers who want to use modules/not use our webpack build to be able to do so.

These are incompatible.

To solve this, we are now writing out the version number into source at release time.
This should have the same effect as before, anyone using an NPM release will get a version number, otherwise you will have 'development'.

I tested this in a release in my fork, you can see the overwritten file here in the artifacts: https://github.com/prestomation/amazon-sumerian-hosts/actions/runs/3301290701
@JuliaABurch JuliaABurch self-assigned this Oct 24, 2022
@JuliaABurch JuliaABurch self-requested a review October 24, 2022 21:27
@prestomation prestomation merged commit 64f40e8 into aws-samples:mainline2.0 Oct 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants