Skip to content
New issue

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

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

Already on GitHub? # to your account

chore: bail rollup and lerna when TS errors [] #299

Merged
merged 1 commit into from
Jan 30, 2024

Conversation

Chaoste
Copy link
Contributor

@Chaoste Chaoste commented Jan 30, 2024

Currently, a TS error does not yield an error when building with rollup.
Using the config noEmitOnError, TS will now return an error that can be consumed by rollup and leads to a subsequent abortion of rollup and lerna.

Video: https://www.loom.com/share/97ba8ed8671f4d5187514b88332bfcd9

Related bug: rollup/rollup-plugin-typescript#43

@Chaoste Chaoste requested a review from dimitrycf January 30, 2024 10:41
@Chaoste Chaoste requested review from a team as code owners January 30, 2024 10:41
Copy link

vercel bot commented Jan 30, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Updated (UTC)
experience-builder-test-app ⬜️ Ignored (Inspect) Jan 30, 2024 10:41am

Copy link
Contributor

@dimitrycf dimitrycf left a comment

Choose a reason for hiding this comment

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

Seems to work great and now aborts build on errors!

image

@dimitrycf
Copy link
Contributor

Actually once I cleared npm cache and rebuilt SDK again it showed this error:

image

We can quick fix it by allowing the coordinates type to accept null (as we don't control de facto value which comes there; and the coordinates is only used in the file for triggering an effect.

image

@Chaoste Chaoste closed this Jan 30, 2024
@Chaoste Chaoste reopened this Jan 30, 2024
@Chaoste Chaoste merged commit f36c8c2 into development Jan 30, 2024
8 of 9 checks passed
@Chaoste Chaoste deleted the fix/fail-build-on-ts-error branch January 30, 2024 14:03
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants