kinow commented on issue #1749: URL: https://github.com/apache/jena/issues/1749#issuecomment-1426854564
> > I will check tomorrow if this issue is easily reproduced on our site with yarn run serve > > so far couldn't reproduce it from yarn :( tried with yarn run serve and yarn run serve:offline Hi @SimonBin Thanks for testing it out. When we run with Yarn, using `vite preview` for instance, the application is built differently than when we run `mvn package`. The latter will perform a production build, that involves some optimization. From the comments from that issue you linked, and after your tests, I think it confirms there's something in the build chain that is causing this loading issue in the generated assets. Here's what I would try (you can try if you have time, but I will do so over next days when I have time): 1. Change `pom.xml` and `package.json` to produce a development build instead of a production build. When you run `yarn run build` or `npx vite build`, you should be able to see a log line like "vite v4.0.4 building for production...". You can change the build mode with `npx vite build --mode development` or `yarn run build --mode development`. You can change the arguments of the Maven execution `yarn run build` of the `frontend-maven-plugin` plug-in. 2. Review the build options of Vite, trying some out and seeing if any fixes the issue (or makes it always happen). 3. Try what was mentioned in the issue you linked. 4. Not my favorite, but sometimes I have to read the source code of Vue/Vite/etc and hack my local copy or check it out and build it locally + link to test things out... just in case nothing fixes it. Cheers -Bruno -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
