Farcaster

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).

* sponsored by Supercast, 25,000 $ANON at a time
* higher rank in Tae Kwon Do than Vladimir Putin
* hobbies include finding new lows of dad jokes

Hmm. Doing that (replacing ~/ with folder traversal references) and adding a global.css file seems to have done the trick.

Well, now the step to add reading of sdk.context broke:

Looks like that step is missing:

  const [isContextOpen, setIsContextOpen] = useState(false);

and:

  const toggleContext = useCallback(() => {
    setIsContextOpen((prev) => !prev);
  }, []);

Let's see if I'm just bad at getting started or can help others get up to speed with this documentation:

Let's see if I'm just bad at getting started or can help others get up to speed with this documentation:

https://github.com/farcasterxyz/docs/pull/392

Full-stack digital product consultant @ BoundCorp.net - eng @daylight

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?

fyi tsconfig.json usually has a line defining these aliases like ~/ or @/, check the tutorials tsconfig

Software engineer, music maker, creator.

Possibly a dog irl

Yeah - if I can find where to do it, I'm going to submit some PRs to correct the docs.