Skip to content

Conversation

@turkycat
Copy link
Contributor

@turkycat turkycat commented Oct 6, 2025

Hey guys, nice work on this project. I'm looking forward to digging deeper!

I found my way here from the 0-to-1 guide on Spark docs and started trying to build things. I had some trouble, but got things working eventually. I took notes of my journey which I'll share below. This PR contains build fixes and suggestions to improve dev workflows on this repo.

If I understand correctly, you guys built some or all of these examples at a hackathon and compiled them together. That's pretty sweet. Lots of good stuff here.

I'm now hacking away with the CLI and express server examples 💪

Notes

These notes may help you understand the path I took to build. If there is anywhere I strayed off the beaten path or you have different advice for this PR or my suggestions, let me know.

Issues I've attempted to resolve are marked with 🟢

  • sdks/js/README.md suggests using nvm use || nvm install but there is no .nvmrc file in the sdks/js directory to specify which Node.js version to use. 🟡
  • apparently mise solves this for this repo, but it's not clear from the READMEs in these example paths that mise is the primary tool manager for this repo. 🟡 -- I added some text about mise, but NVM use could be clarified if not using mise
  • this path is given in https://docs.spark.money/wallet/0-to-1 -- so it should be as simple as the steps given in the docs, but it is not. 🟢
  • several package version conflicts due to monorepo structure. 🟢
  • mise activation performed with eval "$(mise activate bash)" 🟢
  • resolved the package issues with resolutions and upgrades 🟢
  • now I need mise? per missing clang in build fail logfile (I assume installing clang locally would resolve) 🟢
  • nope, clang not part of mise toml. 🟢
  • tried adding clang to mise toml, which -does not- include clang++ and is version 9 (6 years old, oof) -- likely better with system packages anyway 🟢
  • installed clang, resolved some system issues (unrelated to mise/spark) 🟢
  • also had to yarn build in the sdks/js path -- (spark docs cover this, but not README) 🟢
  • a couple endpoints are incorrect in the express example README 🟢

@turkycat
Copy link
Contributor Author

turkycat commented Oct 6, 2025

My fork was out of sync. examples/spark-bare-expo-react-native-app was renamed and the issue I originally had building that was resolved with the recent sync. I've removed my changes to that path as part of the merge.

@turkycat turkycat force-pushed the example-package-resolutions-and-docs branch from 71794c2 to acd70b2 Compare October 6, 2025 02:28
@turkycat
Copy link
Contributor Author

turkycat commented Oct 6, 2025

github was incorrectly rendering the diff including the package changes from examples/spark-bare-expo-react-native-app. I rebased instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant