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: don't publish flow-client TS sources separately in JAR (#10765) (CP: 6.0) #10795

Merged
merged 1 commit into from
Apr 26, 2021

Conversation

Haprog
Copy link
Contributor

@Haprog Haprog commented Apr 26, 2021

Improve performance of webpack build by only shipping precompiled JS of the flow-frontend TS sources, so webpack doesn't try to use the TS source files which is slower than using JS directly. The TS sources are still included in the sourcemaps (.js.map). This is a cherry-pick of 0476cd4 (from master to 6.0).

Improve performance of webpack build by only shipping precompiled JS of the flow-frontend TS sources, so webpack doesn't try to use the TS source files which is slower than using JS directly. The TS sources are still included in the sourcemaps (`.js.map`). This is a cherry-pick of 0476cd4 (from master to 6.0).
@Haprog Haprog added the hilla Issues related to Hilla label Apr 26, 2021
@Haprog Haprog changed the title fix: don't publish flow-client TS sources separately in JAR (#10765) fix: don't publish flow-client TS sources separately in JAR (#10765) (CP: 6.0) Apr 26, 2021
@Haprog Haprog enabled auto-merge (squash) April 26, 2021 08:51
@Haprog Haprog merged commit 06f7417 into 6.0 Apr 26, 2021
@Haprog Haprog deleted the cp-6.0-10765 branch April 26, 2021 11:23
@vaadin-bot
Copy link
Collaborator

This ticket/PR has been released with platform 19.0.7. For prerelease versions, it will be included in its final version.

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

Successfully merging this pull request may close these issues.

3 participants