Skip to content

fix(nextjs): Fix getting sibling package names when testing branch on Vercel #4045

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

Merged
merged 2 commits into from
Oct 11, 2021

Conversation

lobsterkatie
Copy link
Member

Oh, the difference a $ can make...

(Specifically, it's the difference between actually retrieving the value of a variable and mistakenly using said variable's name as the value. Whoops.)

@github-actions
Copy link
Contributor

github-actions bot commented Oct 11, 2021

size-limit report

Path Size
@sentry/browser - CDN Bundle (gzipped) 22.34 KB (0%)
@sentry/browser - Webpack 23.31 KB (0%)
@sentry/react - Webpack 23.34 KB (0%)
@sentry/browser + @sentry/tracing - CDN Bundle (gzipped) 29.79 KB (0%)

@kamilogorek
Copy link
Contributor

Eh, and it was even correctly not highlighted, my bad 🥲

@lobsterkatie
Copy link
Member Author

Eh, and it was even correctly not highlighted, my bad

Honestly, I think it was my mistake. My brain might know bash, but my fingers don't quite yet.

@lobsterkatie lobsterkatie merged commit 597ed4a into master Oct 11, 2021
@lobsterkatie lobsterkatie deleted the kmclb-nextjs-fix-vercel-sibling-linking branch October 11, 2021 16:05
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.

2 participants