gatsby-dev-cli doesn't copy over package dependencies, which means manually installing those dependencies into your test sites.
Explore how best to fix this or document a work around.
Can this be fixed with symlinking? Will that mess with yarn / npm's module resolution. What are other ways to handle this.
my approach currently is to npm pack package when I change dependencies and install resulting tarball in test site (which will handle dependencies) before running gatsby-dev - not cleanest and require some manual work but it does the trick
That sounds good! Would it be possible for gatsby-dev-cli to do that automatically?
Verdaccio is often used for this. This SO answer gives examples of how other project have configured it: https://stackoverflow.com/questions/50206729/how-to-test-an-npm-publish-result-without-actually-publishing-to-npm#50222427
Hiya!
This issue has gone quiet. Spooky quiet. 馃懟
We get a lot of issues, so we currently close issues after 30 days of inactivity. It鈥檚 been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
Thanks for being a part of the Gatsby community! 馃挭馃挏
Hey again!
It鈥檚 been 30 days since anything happened on this issue, so our friendly neighborhood robot (that鈥檚 me!) is going to close it.
Please keep in mind that I鈥檓 only a robot, so if I鈥檝e closed this issue in error, I鈥檓 HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.
Thanks again for being part of the Gatsby community!