-
Notifications
You must be signed in to change notification settings - Fork 140
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
Bug report: Issue with rrweb dependency when compiled for typescript app #1437
Comments
I have the same error. |
Same issue with version |
any update on this issue, its present on 1.167.0 as well |
This issue starts for me in 1.164.0 - so it was probably this #1413 |
version 1.174.2
|
Signed-off-by: Michael Telatynski <[email protected]>
* Update all non-major dependencies * Pin posthog-js back due to PostHog/posthog-js#1437 Signed-off-by: Michael Telatynski <[email protected]> --------- Signed-off-by: Michael Telatynski <[email protected]> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Michael Telatynski <[email protected]>
Are there any updates or workarounds for this issue? The build still breaks with Posthog 1.190.2?
|
@PostHog Any progress on this issue? The build is still breaks with 1.200.1 |
still broken in 1.203.1. |
can folk share what version of node and TS they're using? we're importing posthog-js in a CI test to validate minimum supported TS version and don't get this error, so, since I can't repro it i can't suggest a fix 😅 |
node -v I personally downgraded to posthog-js: 1.181.0, as was suggested in other thread, and it works now. |
Setting |
considering existing compile time bug that has been happening for the last 3 month since 1.164.0 (last stable version was 1.163.1). PostHog/posthog-js#1437
considering existing compile time bug that has been happening for the last 3 month since 1.164.0 (last stable version was 1.163.1). PostHog/posthog-js#1437
We get the following error when trying to compile our typescript app using posthog-js.
Seems to have been introduced with v1.164.0
The text was updated successfully, but these errors were encountered: