Hi Ragunath,
Many thx for the answer.
It is definitely a great help to have the license code in separate file or in the environment, this solves the problem how to not check it into git, so the license will not exposed to the source control.
I've read the documentation link, you pointed, what is not clear for me, what kind of "trick" will do the
npx syncfusion-license activate
I mean, a) will it then only check the valid license _build_ time, so the webpacked site will not contain any license related secret, or b) it will embed the key somehow to the final webpacked result, so the site still will check it runtime, when the browser are using the SPA.