Closed marcelovicentegc closed 1 week ago
Sorry, I didn't mean to close this issue with the PR referencing it on the other repo :smile:
It may be related to the pnpm 9 update. I fixed by re-enabling the link-workspace-packages https://github.com/pnpm/pnpm/releases/tag/v9.0.0.
Also, typescript version update seems to help on this. Closing for now, we will reopen if the issue continues
Summary
Not sure yet if we can generalize, but the direct use of ariakit (Menu) + Shoreline components that depend on it (Popover), break apps (Next.js application 14) :exploding_head:
I caught this while dealing with a merge between two PRs (https://github.com/vtex/admin-platform/pull/140 and https://github.com/vtex/admin-platform/pull/162), both working separately, but breaking when merged. One PR implementing changes which require direct use of ariakit's Menu component, and the other PR implementing changes which make indirect use of ariakit's Popover components.
The error Internal error: TypeError: render is not a function (stack trace below)
The
render
function is available at both ariakit versions used directly (0.4.7, https://github.com/vtex/admin-platform/pull/140) and indirectly, via Shoreline (0.4.5, https://github.com/vtex/admin-platform/pull/162).Tested the following:
The paliative resolution was to change the PR which made use of ariakit indirectly and make direct use of it. This worked.
Expected behavior
Direct and indirect use of ariakit on applications should work seamlessly.
Current behavior
Reproducible Example
:loading:
Suggested solution
Upgrade ariakit version to latest (0.4.7).
Additional context
No response
Package
@vtex/shoreline
Packages version
1.0.0-rc.46
Browser
Brave
Package Manager
pnpm