customModule not loaded when using the query parameter

[spycherf-BCUFR]

Hello,

Since January, I have been unable to load the customModule when using "npm run start" and accessing with the query parameter &useLocalCustomPackage=true, e.g.:
https://slsp-bcufr.primo.exlibrisgroup.com/nde/home?vid=41SLSP_BCUFR:DFR_NDE_test&useLocalCustomPackage=true
This happens both in the production and sandbox environments.

The customModule is loaded fine when using "npm run start:proxy" and accessing via localhost:4201. The problem is that localhost is not accepted by some APIs, so to develop certain components, I need to use the method with the query parameter.

It was working fine last year, and after the holidays, the problem appeared (even though my code hadn't changed).
Thanks for looking into this.

Kind regards,

F. Spycher

[ShoulM]

Hi could you share your custom module so I could try and reproduce the issue?

[spycherf-BCUFR]

Hi Shoul, here it is: customModule_41SLSP_BCUFR_DFR_NDE_test.zip

For now, it contains mostly tests so there's a lot of "garbage", but the code under /app or /assets shouldn't be the reason behind the problem, as the module works fine with the proxy.
Thanks for your help in this matter.

Update @ShoulM : Just to let you know that I tried again with a quasi-OOB customModule, replacing only the NDE landing page with a test component; and getting the same result: the test component appears with npm run start:proxy + accessing via localhost, and doesn't when using npm run start + accessing the live URL and &useLocalCustomPackage=true.

customModuleTest.zip

Here are the console logs with and without the query parameter:

console_withparam.log
console_noparam.log

Could that first error have anything to do with the issue?

bootstrap-config.ts:40 GET https://slsp-bcufr.primo.exlibrisgroup.com/nde/custom/41SLSP_BCUFR-DFR_NDE_test/CENTRAL_CODE.txt 404 (Not Found)

[spycherf-BCUFR]

Dear @ShoulM ,

A quick update to let you know that the issue is still ongoing.

However, I have found a workaround to still be able to use APIs with the proxy, by adding specific Angular environments for production and development (and a related fileReplacements in angular.json), as well as some retargeting rules in the proxy. This allows me to use npm run start:proxy and have the local dev environment fully functional.

Here is the code if other people are facing the same issue and are in need of a workaround:

environment.dev.ts

export const environment = {
  production: false,
  bcuApiUrl: '',
  webappsUnifrApiUrl: ''
};

environment.ts

export const environment = {
  production: true,
  bcuApiUrl: 'https://...',
  webappsUnifrApiUrl: 'https://...'
};

angular.json

"configurations": {
	"development": {
		"fileReplacements": [
			{
				"replace": "src/environments/environment.ts",
				"with": "src/environments/environment.dev.ts"
			}
		],

proxy.const.mjs

const proxyRules = [
  {
    context: ['/bcu_api'],
    target: 'https://...',
    secure: true,
    changeOrigin: true,
    logLevel: 'debug',
  },
  {
    context: ['/bcu/primo'],
    target: 'https://...',
    secure: true,
    changeOrigin: true,
    logLevel: 'debug',
  },

Example of use inside a component

const apiUrlBase = `${environment.bcuApiUrl}/bcu_api/libraries/${apiLang}`;

Ex Libris might still want to look at the issue (if you've been able to reproduce it in an consortial environment); as things currently stand, the following line of the README is "false advertisement" ;)

Add the following query parameter to your NDE URL: useLocalCustomPackage=true For example: https://sqa-na02.alma.exlibrisgroup.com/nde/home?vid=EXLDEV1_INST:NDE&useLocalCustomPackage=true

Kind regards,

Frederic

[FaigySaberski]

Hello @spycherf-BCUFR,

Thank you for the detailed report.
We have opened a bug for this issue. The team will review and schedule it for one of the next sprints based on prioritization.