[Next] Allow customisation of the styled system import

[JakeGinnivan]

My project has a different config so the styled-system import from the root doesn't work, so I have to edit each file to fix the import after I add the component.

Also was thinking styled-system-import-prefix, which could just be ./app/ or something.

[vercel]

@JakeGinnivan is attempting to deploy a commit to the Personal Team on Vercel.

A member of the Team first needs to authorize it.

[cschroeter]

@JakeGinnivan That’s actually a pretty solid idea. I’m just not entirely sure if it’s the right approach.As I can see folks want to customize the location of the tsconfig, while the other case is about the panda config path.

Maybe a hook-based approach would be more flexible, similar to how you can tweak the Vite build config. I will keep it open though as it is not a bad approach

[Guria]

In my setup I rely on "native" package.json exports and imports configuration. It forces to use # at beginning.

[JakeGinnivan]

@cschroeter yeah, it's a pretty naive solution, but thought it'd throw something up. Maybe could introduce as unstable_imports, with a note implementation may change so we can solve the issue, but then come up with a better solution or improve it.