So, I've been going over the online documentations to make sure that I'm not asking a dumb question here. While there's been mention within the docs that we can set up the value of the license key as an environment variable. The instructions surrounding it isn't clear enough. By 'environment variable' do you mean like how we sometimes would set up a path for an executable in the windows system environment? Or in Ubuntu/Linux we would use .bashrc file. I usually put my environment variables there.
Is that what the docs is referring to?
The other thing that I'm also really curious to ask, when following the "Getting Started" guide within the docs, I was trying to set up an app using "npx create-kendoreact-app". But I encountered an error when it tried to download/install various components. I suspect it might be something to do with the licensing? I could be wrong. (I've attached the image) I'm not sure if this is the normal behavior, or maybe it's just a random, one-time incident.
(Updated) I have given 'npx create-kendoreact-app' another shot. This time I didn't opt for SASS, and everything ran smoothly. Perhaps you might want to raise this issue within your product team. Let them know that it needs to be fixed.
Curious, for all future KendoReact projects, does it mean we have to do two steps?
- Step One: run npx create-kendoreact-app
- Step Two: run npx kendo-ui-license activate
I look forward to your clarification on these two issues.
(Updated) Sorry, I seemed to have answered my own question. Yes, the environment variable as stated in the docs meant putting it in an actual Environment Variable on your system.
On Linux: Edit the .bashrc file in your home folder.
On Windows: Just create a new environment variable and call it "KENDO_UI_LICENSE".
I want to leave this here for anybody it might help in the near future. :P
Hello, Sherman,
Thanks a lot for the feedback and the shared solutions with our community - I am really glad you managed to resolve the initial problems and everything works smoothly now.
Vessy
Not a problem. I'm just glad I was able to figure it out on my own. There is still the issue with the error that happens when a developer selects "Yes" to the SASS option. Probably should get the team to look into that.
Sherman
Sure, Sherman, I will definitely pass this issue to the team.
Vessy