Problem in installing Kolibri as local development setup

Summary

I am trying to do local setup on my Windows 11 .
After I created virtual environment with Node@10.17.0 , my npm is repeatedly giving error as saying “npm not supported with this specific version of Nodejs”…
But I have already installed Node@10 and npm package comes within it…

Technical details

  • Kolibri version - v0.15.x
  • Operating system - Windows 11
  • Browser - Chrome
(kolibri) C:\Users\varun\Desktop\Code\Vs_code\kolibri>nodeenv -p --node=10.17.0
 * Install prebuilt node (10.17.0) ..... done.
 * Overwriting C:\Users\varun\Desktop\Code\Vs_code\kolibri\Scripts\activate.bat with new content
 * Overwriting C:\Users\varun\Desktop\Code\Vs_code\kolibri\Scripts\deactivate.bat with new content
 * Overwriting C:\Users\varun\Desktop\Code\Vs_code\kolibri\Scripts\Activate.ps1 with new content
symbolic link created for C:\Users\varun\Desktop\Code\Vs_code\kolibri\Scripts\nodejs.exe <<===>> node.exe
 * Install npm.js (latest) ...
(kolibri) C:\Users\varun\Desktop\Code\Vs_code\kolibri>
(kolibri) C:\Users\varun\Desktop\Code\Vs_code\kolibri>npm --version
ERROR: npm v9.6.3 is known not to run on Node.js v10.17.0.  This version of npm supports the following node versions: `^14.17.0 || ^16.13.0 || >=18.0.0`. You can find the latest version at https://nodejs.org/.

ERROR:
C:\Users\varun\Desktop\Code\Vs_code\kolibri\Scripts\node_modules\npm\lib\utils\exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token .
    at Module._compile (internal/modules/cjs/loader.js:723:23)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at module.exports (C:\Users\varun\Desktop\Code\Vs_code\kolibri\Scripts\node_modules\npm\lib\cli.js:42:23)
    at Object.<anonymous> (C:\Users\varun\Desktop\Code\Vs_code\kolibri\Scripts\node_modules\npm\bin\npm-cli.js:2:25)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
ERROR: npm v9.6.3 is known not to run on Node.js v10.17.0.  This version of npm supports the following node versions: `^14.17.0 || ^16.13.0 || >=18.0.0`. You can find the latest version at https://nodejs.org/.

ERROR:
C:\Users\varun\Desktop\Code\Vs_code\kolibri\Scripts\node_modules\npm\lib\utils\exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token .
    at Module._compile (internal/modules/cjs/loader.js:723:23)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at module.exports (C:\Users\varun\Desktop\Code\Vs_code\kolibri\Scripts\node_modules\npm\lib\cli.js:42:23)
    at Object.<anonymous> (C:\Users\varun\Desktop\Code\Vs_code\kolibri\Scripts\node_modules\npm\bin\npm-cli.js:2:25)
    at Module._compile (internal/modules/cjs/loader.js:778:30)

Hi @varunsh17,

Welcome to the forums! Are you intending to contribute to Kolibri development? If so, we highly recommend using WSL. Development directly within Windows isn’t supported at this time.

If you’re looking to simply install Kolibri, you may choose the appropriate installer from our downloads page.

Regards,
Blaine

I want to create develpment environment…
Sure I will create it in WSL
One, thing which version should I develop all my local evn ?
Devlop branch or release-v0.15.x ??

Hi @varunsh17,

You may skip the section ‘Checkout release-v0.15.x’ in the developer documentation, and use the develop branch. Those instructions are no longer valid, as we’ve completed the updates to Kolibri’s setup flow.

We’ll also be updating the documentation to remove that

-Blaine

(kolibri-py3.9) varun@DESKTOP-42OA54B:~/Code/kolibri$ nodeenv -p --node=16.13.2
 * Install prebuilt node (16.13.2) ..... done.
 * Appending data to /home/varun/.pyenv/versions/3.9.9/envs/kolibri-py3.9/bin/activate
 * Appending data to /home/varun/.pyenv/versions/3.9.9/envs/kolibri-py3.9/bin/activate.fish
(kolibri-py3.9) varun@DESKTOP-42OA54B:~/Code/kolibri$ nodeenv --version
1.3.3

Node version isn’t changing in WSL
Here’s the doc that I followed as per develop branch

(kolibri-py3.9) varun@DESKTOP-42OA54B:~/Code/kolibri$ npm --version
9.5.0
(kolibri-py3.9) varun@DESKTOP-42OA54B:~/Code/kolibri$ node --version
v18.15.0

Running nodeenv -p --node=16.13.2 is only downloading but not setting is for python virtual environment…
How to fix this ?
Thanks for replying @blaine

Hi @varunsh17,

Could you try restarting your shell and then activating your virtualenv again? You’ll need to do so after running the nodeenv command and installing yarn. You should see something like this after restarting:

$ which node
/home/bjester/.pyenv/shims/node
$ which yarn
/home/bjester/.pyenv/shims/yarn

Successfully running the dev server…All thanks to you @blaine .
Where should I start contributing, as I see there are no good first issues on the repo.
It would be helpful if you would suggest something.

Hi @varunsh17,

I see you found at least on issue to work on!

1 Like