chore(atomic): update getAssetPath

[y-lakhdar]

Update the logic to handle asset paths without the need of Stencil. The logic is based on Stencil/core's getAssetPath function, where the resourceUrl is dynamically determined based on how the app is built.

Logic

When served from a CDN, the resourceUrl is computed based on the file location (import.meta.url). This value is injected at build time via a TypeScript custom transformer.
Otherwise, it is computed from the document location.

Test Configuration Update:

• packages/atomic/vitest.config.ts: Updated the test configuration to define import.meta.env.RESOURCE_URL.

https://coveord.atlassian.net/browse/KIT-3944

[github-actions]

Pull Request Report

PR Title

✅ Title follows the conventional commit spec.

Live demo links

• Storybook

• Playwright report

Bundle Size

File	Old (kb)	New (kb)	Change (%)
case-assist	243.7	243.7	0
commerce	355	355	0
search	415	415	0
insight	406.2	406.2	0
recommendation	255.9	255.9	0
ssr	408.8	408.8	0
ssr-commerce	372.7	372.7	0

[alexprudhomme]

is this really a feature ?

[louis-bompart]

How does the assetPath works for NPM user today, and how would it works afterward?

[y-lakhdar]

How does the assetPath works for NPM user today, and how would it works afterward?

For NPM users today, if the iconAssetsPath attribute on the search interface is left unchanged, the getAssetPath method retrieves assets from the default folder using a relative path (e.g., /assets/[icon] for icons).

This behavior remains the same moving forward. Since the RESOURCE_URL environment variable is only set when building for CDN, the asset base URL continues to be determined based on the browser’s location.

[alexprudhomme]

How does the assetPath works for NPM user today, and how would it works afterward?

For NPM users today, if the iconAssetsPath attribute on the search interface is left unchanged, the getAssetPath method retrieves assets from the default folder using a relative path (e.g., /assets/[icon] for icons).

This behavior remains the same moving forward. Since the RESOURCE_URL environment variable is only set when building for CDN, the asset base URL continues to be determined based on the browser’s location.

So technically RESOURCE_URL could be any string or any variable since it is undefined in the npm build and replaced in the cdn one ?

Also, this is not a feature, you should change the pr title.

[louis-bompart]

I think that's fine.
However, QA Approval will be mandatory for this one

[alexprudhomme]

lets try it !

[fpbrault]

🚀