proxy assets

[uleodolter]

currently assets are not handled when running in proxy mode ( npm run start:proxy )

i tried to replace library-logo.png and placed custom logo in src/assets/images/library-logo.png

after running in proxy mode i can access the logo from http://localhost:4201/assets/images/library-logo.png

when accessing http://localhost:4201/nde/home?vid=... the logo location looks like http://localhost:4201/nde/assets/images/library-logo.png

therefore i tried to modify proxy/proxy.conf.mjs and added

  {
    context: [
      '/nde/assets/**'
    ],
    target: 'not-needed',
    router: (req) => {
      const url = `${req.protocol}://${req.get('host')}`
      console.log(url);
      return url;

    },
    secure: true,
    logLevel: 'debug',
    pathRewrite: { '^/nde/assets/': '/assets/' },

  },

this resulted to proxy all assets, the local library logo is shown correctly, but all other default assets are missing.

how can we proxy local assets (if they exist, .e.g. library-logo.png, homepage.css, homepage_de.html, ...) and still access missing assets from default location (alma/primo platform) ?

this would be great for developing / testing the customization of the home page.

[mdavismcd]

I'm running into the same issue as stated above.
changes to src\assets\homepage\homepage_en.html (after removing .tmpl) aren't serving using the proxy.

[BerrisfordEdwards]

I'm experiencing the same issue. It would appear that the proxy setup is broken(?)
Also, when I use the second option mentioned (URL parameter), my project appears to build properly, but I get just a blank screen with a single error message in the console: "Uncaught SyntaxError: Cannot use 'import.meta' outside a module (at styles.js:8065:29)". Any help/ideas please?

[ShoulM]

Hi assets are now handled when using the proxy to preview. Closing this issue.