Bring pool creator

[agualis]

Pool creator is an standalone project that is currently copy-pasting some of the code from V3 monorepo. We should:
A. Move the pool creator inside the mono-repo
or
B. Extract am npm library to share the common code that the current pool creator is duplicating.

[agualis]

cc @MattPereira

[MattPereira]

Hey not currently copy pasting code from v3 monorepo since I haven't had time to hook up the user token wallet balances yet. Got tied up with other more critical issues

Open to moving pool creator into monorepo but you are aware the scaffold stack is nextjs / wagmi / viem / tanstack / tailwind / daisyui right?

[garethfuller]

@MattPereira we're using Turborepo so having different dependencies won't be a problem. They'll just be dependencies of your app.

[MattPereira]

oh sweet then I guess decision comes down to if reward of moving scaffold into v3 monorepo is worth the trouble ?
( this is just me guessing 😅 )

Costs

• Vercel deployment would need to be changed
• Risk of additional complexity as scaffold itself is a yarn workspaces monorepo so may need some re-configuration?

Benefits

• Scaffold could borrow things like rpc urls and react hooks from v3 FE?
• Fewer balancer repos floating around

[garethfuller]

I think eventually pool creation will be brought within the main app and the cost of managing another app within the monorepo for now isn't worth it. We can revisit this later.