Content
@
0 reply
20 recasts
20 reactions
Joshua Hyde (he/him) ツ
@jrh3k5.eth
Trying to get started with Frames v2 and having issues with the guide here: https://docs.farcaster.xyz/developers/frames/v2/getting-started Had to install Next manually since it didn't happen automatically. After i resolved that, when I run yarn dev, I get the attached error. The use of the ~/ placeholder seems to break in code - should I be replacing all of the references with relative paths (e.g., ../) for each component? That seems to satisfy the compiler, but I hesitate to deviate from the tutorial so early on (especially since I know next to nothing about React development).
5 replies
1 recast
7 reactions
Leeward Bound
@leewardbound
fyi tsconfig.json usually has a line defining these aliases like ~/ or @/, check the tutorials tsconfig
1 reply
0 recast
0 reaction
Joshua Hyde (he/him) ツ
@jrh3k5.eth
Question from a Typescript noob: would it be sensible to submit a PR to change these references to relative file paths? Would that make the example code more portable, or is that just swimming hard upstream against dev conventions?
1 reply
0 recast
1 reaction