Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Path to static resources is baked in, cannot be set when using as a module

See original GitHub issue

When using the GUI as a node module in another project, you should be able to specify where to find static assets like images. Right now they are baked with /static/assets/... which works for www but makes it hard to use in other projects where those files might have a different path.

/cc @rschamp part of using GUI as a component of other projects

Issue Analytics

State:
Created 5 years ago
Comments:12 (12 by maintainers)

Top GitHub Comments

2reactions

rschampcommented, Feb 28, 2019

I’m not sure what the best way to solve this is for the distributable module, but for our purposes in the short term the plan should be to inline loaders and point main (or just browser) to src/ so that the gui can be built by an external webpack config. Then the containing project can configure publicPath itself.

0reactions

chrisgarritycommented, Mar 13, 2019

Setting __webpack_public_path__ would work if we were building different versions of gui. Unfortunately, we’re building a consumer of gui (i.e. www and desktop), and the version of gui they use is already built (dist) and the static path for assets is already set. So the real solution is to use src/index.js as a browser entry point and let the consumer projects configure the static path and build gui as mentioned by @rschamp above. However, that would be a pretty big change for scratch-www, so for now the workaround is https://github.com/LLK/scratch-gui/pull/4646