🐛(frontend) posthog-cli 0.5.0 release introduced breaking changes
Posthog-cli version wasn't pinned. Please check issue #39846, which describe our issue, starting 0.5.0, the cli needs an API token and a Project ID. Pin to the last stable version we used 0.4.8, and wait a bit they already released a 0.5.1 that mitigate some of the breaking change. I would wait the 0.5.x to be stable and battle tested by other developpers before switching. Also as I consider switching the Error tracking to sentry.
This commit is contained in:
committed by
aleb_the_flash
parent
06a5b9b17e
commit
df671ea994
@@ -24,7 +24,7 @@ RUN npm run build
|
|||||||
# Inject PostHog sourcemap metadata into the built assets
|
# Inject PostHog sourcemap metadata into the built assets
|
||||||
# This metadata is essential for correctly mapping errors to source maps in production
|
# This metadata is essential for correctly mapping errors to source maps in production
|
||||||
RUN set -e && \
|
RUN set -e && \
|
||||||
npx @posthog/cli sourcemap inject --directory ./dist/assets
|
npx @posthog/cli@0.4.8 sourcemap inject --directory ./dist/assets
|
||||||
|
|
||||||
COPY ./docker/dinum-frontend/dinum-styles.css \
|
COPY ./docker/dinum-frontend/dinum-styles.css \
|
||||||
./dist/assets/
|
./dist/assets/
|
||||||
|
|||||||
Reference in New Issue
Block a user