Missing reference in CSS file "tabcontent.css" about js9 HOT 3 CLOSED

@srggrs Thanks! This error,(which does not show up in either the FF or Chrome debugger) has been fixed in my working directory and will be updated this week.

I assume you can simply edit js9support.css and change the paths as a work-around ... but let me know if that presents a problem.

cc: @miguelcarcamov

from js9.

my understanding is that compiling JS9 as suggested in the documentation is meant for setting up the assets in the "build" folder.

Yes, JS9 stuff gets installed in two places:

1. binaries and scripts get installed somewhere in the *nix system so that they are accessible to the js9Helper (i.e., accessible to whichever user runs the helper). Without --prefix, your binaries went into the default /usr/local

2. web stuff gets installed in a directory located in a web server's directory structure, to service the JS9-enabled web page

It's great that whitenoise found the incorrect links, they have been wrong for about 7 years ...

from js9.

@ericmandel no worries. It's not a big deal! Just trying to understand how I can "productionise" JS9 assets: my understanding is that compiling JS9 as suggested in the documentation is meant for setting up the assets in the "build" folder. Then ideally you have a script that would move specific files (e.g. js9.css) in a "static_prod" folder to serve the production server. In doing so I'd would expect the references to other files would be fixed (e.g. if I copy the css file, font and images folders, I'd expect all the references are as the build folder), so that I don't need to manually change them 😅 .

At the end it is just convenient if all the references are right so I can set up an automatic CI/CD pipeline for my app with JS9.

Thank you so much for looking into that 😄

from js9.