-
Notifications
You must be signed in to change notification settings - Fork 242
make mapbox tutorial work #228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Holy shit that's a diff. Why are we checking in all these dependencies? And why do we seem to have a bunch of mapbox tests? Are they part of their npm package? |
Yeah. It's not packaged very well |
We could avoid checking |
Regardless of how it's packaged, something still feels very wrong about checking these all into the repo. I see we're only gitignoring |
Good idea, some predev/build script that downloads a fixed version into the respective folders would be great |
As I say, forcing it to be visible is arguably a good thing in this context. We wouldn't be having this conversation if it hadn't been done that way! I'd much rather we find a way to bundle |
Personally, I would be against committing minified So I think it would be better to write a script that pre-builds and copies the code, and run it at the same time of running In the case of this tutorial, it seems to work with only |
going to close this since the mapbox example has been replaced with George Nees https://learn.svelte.dev/tutorial/context-api |
this fixes #124... at a cost. It has a sprawling dependency graph so we end up adding a lot of stuff to
node_modules
, which has to be downloaded. Maybe we can bundle it better, or maybe installing it withturbo
(the WebContainernpm
stand-in) would work. Will investigate further