Errors building suttacentral development environment, the sequel 🤖

Snowbird · February 14, 2024, 8:14pm

[Public service announcement: If you never want to see Meta posts in your feed, just go to that category and click the bell icon on the far right. Then choose “Muted”. All posts in that category will stop appearing in your feed.]

I’m trying to do the same thing @josephzizys was doing in this thread, but I thought it would be better to start a new thread since I have different issues.

I have setup WSL2 on a Windows 11 machine, with Ubuntu (through the Windows Store). Docker is installed successfully and I have cloned the repository.

I’m at step 3 on these instructions:

run make prepare-host in order to make some small adjustment on the host machine.

I am getting this brief message at the cli:

npm ERR! code CERT_HAS_EXPIRED
npm ERR! errno CERT_HAS_EXPIRED
npm ERR! request to https://registry.npm.taobao.org/yocto-queue/download/yocto-queue-0.1.0.tgz?cache=0&sync_timestamp=1606290282107&other_urls=https%3A%2F%2Fregistry.npm.taobao.org%2Fyocto-queue%2Fdownload%2Fyocto-queue-0.1.0.tgz failed, reason: certificate has expired

npm ERR! A complete log of this run can be found in: C:\Users\lea\AppData\Local\npm-cache\_logs\2024-02-14T19_35_47_683Z-debug-0.log
make: *** [Makefile:8: prepare-host] Error 1

Using help from ChatGPT…

Ran npm install -g npm@latest
Ran npm cache clean --force

Those seemed to go ok

Re-ran make prepare-host

This time the output in the terminal was much shorter, I’m assuming because most things were already installed.

But I still got the same error as above.

When I look in the log, I see this:

[…lots cut out…]
4604 verbose cwd \\wsl.localhost\Ubuntu\home\learning\suttacentral\client
4605 verbose Windows_NT 10.0.22631
4606 verbose node v18.17.1
4607 verbose npm  v10.4.0
4608 error code CERT_HAS_EXPIRED
4609 error errno CERT_HAS_EXPIRED
4610 error request to https://registry.npm.taobao.org/yocto-queue/download/yocto-queue-0.1.0.tgz?cache=0&sync_timestamp=1606290282107&other_urls=https%3A%2F%2Fregistry.npm.taobao.org%2Fyocto-queue%2Fdownload%2Fyocto-queue-0.1.0.tgz failed, reason: certificate has expired
4611 verbose exit 1
4612 timing npm Completed in 103575ms
4613 verbose unfinished npm timer reify 1707939892314
4614 verbose unfinished npm timer reify:unpack 1707939893943
4615 verbose unfinished npm timer reifyNode:node_modules/yocto-queue 1707939893944
4616 verbose unfinished npm timer reifyNode:node_modules/yargs-parser 1707939893944
4617 verbose unfinished npm timer reifyNode:node_modules/yallist 1707939893945
4618 verbose unfinished npm timer reifyNode:node_modules/y18n 1707939893945
[…lots cut out…]

Here is the whole log file.

Ideas? Can I ignore this and move on? Or are all those verbose unfinished npm things that follow it in the log indicating that they are also not installed?

Khemarato.bhikkhu · February 14, 2024, 11:39pm

It’s not you. Their SSL (HTTPS) Certificate really has expired. The best solution is if they update their cert soon… I’d probably just wait. Alternative is to find a mirror and point npm to that.

Here is a list of npm mirrors

And the StackOverflow on how to change your mirror

Snowbird · February 14, 2024, 11:50pm

So do you mean wait to continue with the rest of the project of building my local version, or just proceed with things as they are and ignore the error.

I don’t really understand what’s going on with this script, that’s why I’m not sure. Is it just (at least in this case) trying to update things that are already there? So I would just be using some old version?

Thanks, as always!

Khemarato.bhikkhu · February 15, 2024, 12:18am

You could continue on but I suspect that this is trying to install required dependencies so you might not get far.

It turns out to be one line to change the mirror so… just try it?

Snowbird · February 15, 2024, 1:05am

I’ve tried all the mirrors and they all end up with the same error. One thing I don’t understand is in the error message it has

request to https://registry.npm.taobao.org/yocto-queue/download/yocto-queue-0.1.0.tgz?

But https://registry.npm.taobao.org/ is one of the mirrors? And it has always been trying to go there no matter what mirror I’m using?

It appears to be trying do download yocto-queue-0.1.0.tgz which according to what I think is its npm page, is an old version. But that version has supposedly been downloaded 32m times in the last 7 days.

I have run npm config get registry to be sure I have actually changed registries.

If I do try to proceed with the rest of the instructions, could I do damage to what I have already done? The next step is

1st time run: run make run-preview-env - Build images, load data, index-arangosearch and more.

normal run: run make run-dev.

Khemarato.bhikkhu · February 15, 2024, 1:38am

Ah! Try deleting the lock file first:

rm client/package-lock.json

and then try again?

Snowbird · February 15, 2024, 2:27am

Ooh… Progress in the form of a new error?

I ran that command and then re-ran make prepare-host

I ended up with this error:

npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno -4058
npm ERR! enoent An unknown git error occurred
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in: C:\Users\learn\AppData\Local\npm-cache\_logs\2024-02-15T01_42_41_163Z-debug-0.log
make: *** [Makefile:8: prepare-host] Error 38

Using ChatGPT I got the advice that git might not be in my environment variables, so I put it there and tested by outputting them. This is how that output started:

$ echo $PATH
/usr/bin/git:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib

Then it goes on to list the Windows environment variables which I am told is to be expected with my setup of WSL2.

How I added it and more fun

I did nano ~/.bashrc and added

export PATH="/usr/bin/git:$PATH"

Honestly I’m not sure any of this was needed since it already had /usr/bin in my environmental variables.

I also opened .profile and saw it had this:


# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/.local/bin" ] ; then
    PATH="$HOME/.local/bin:$PATH"
fi

When I was all done I did source ~/.bashrc to make sure it was recognized.

However doing this did not help. I ran the error message through ChatGPT and I’m not sure how to procede.

Khemarato.bhikkhu · February 15, 2024, 2:35am

Is not very helpful for this kind of thing. It’s going to give you generic advice and you need some targeted debugging.

What does that debug-0.log file say?

Khemarato.bhikkhu · February 15, 2024, 2:40am

In addition to those steps, someone is suggesting to make sure npm is up to date: npm install -g npm@latest

BethL · February 15, 2024, 1:41pm

Hmmm…this seems like a very very very high priority

Snowbird · February 15, 2024, 8:54pm

This shouldn’t affect SuttaCentral in any way, as I understand. It’s just that the build script on my machine isn’t able to get a package.

I think I have all the errors sorted thanks to ven. @Khemarato.bhikkhu

It appears that WSL2 is supposed to be using git and npm from the Windows side. By adding a path variable and by removing some (export PATH=$(echo "$PATH" | sed -e 's%:/mnt/c/Program Files/nodejs%%' -e 's%:/mnt/c/Users/learn/AppData/Roaming/npm%%') and installing npm on the Ubuntu side I was eventually able to force WSL2 to use what it had on the Ubuntu side.

Running make prepare-host finally worked successfully, but with a lot of warnings. See below if you care. 105 alltogether.

`make prepare-host` warnings

$ make prepare-host
Setting up client/ git-hook
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@orama/orama@2.0.6’,
npm WARN EBADENGINE required: { node: ‘>= 16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@orama/stemmers@2.0.6’,
npm WARN EBADENGINE required: { node: ‘>= 16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@orama/stopwords@2.0.6’,
npm WARN EBADENGINE required: { node: ‘>= 16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@rollup/plugin-babel@6.0.4’,
npm WARN EBADENGINE required: { node: ‘>=14.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/dev-server-legacy@2.0.0’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/test-runner@0.16.1’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘babel-loader@9.1.2’,
npm WARN EBADENGINE required: { node: ‘>= 14.15.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘copy-webpack-plugin@11.0.0’,
npm WARN EBADENGINE required: { node: ‘>= 14.15.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘eslint-plugin-compat@4.2.0’,
npm WARN EBADENGINE required: { node: ‘>=14.x’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘eslint-plugin-prettier@5.1.3’,
npm WARN EBADENGINE required: { node: ‘^14.18.0 || >=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘prettier@3.1.1’,
npm WARN EBADENGINE required: { node: ‘>=14’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘husky@8.0.3’,
npm WARN EBADENGINE required: { node: ‘>=14’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest@29.5.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘lint-staged@13.3.0’,
npm WARN EBADENGINE required: { node: ‘^16.14.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘mocha@10.3.0’,
npm WARN EBADENGINE required: { node: ‘>= 14.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘vite@4.5.1’,
npm WARN EBADENGINE required: { node: ‘^14.18.0 || >=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘vite-plugin-pwa@0.16.4’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘webpack-cli@5.1.4’,
npm WARN EBADENGINE required: { node: ‘>=14.15.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘workbox-webpack-plugin@7.0.0’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@rollup/pluginutils@5.1.0’,
npm WARN EBADENGINE required: { node: ‘>=14.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/dev-server-core@0.5.2’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/polyfills-loader@2.2.0’,
npm WARN EBADENGINE required: { node: ‘>=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/parse5-utils@2.1.0’,
npm WARN EBADENGINE required: { node: ‘>=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘isbinaryfile@5.0.2’,
npm WARN EBADENGINE required: { node: ‘>= 18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘lru-cache@8.0.5’,
npm WARN EBADENGINE required: { node: ‘>=16.14’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/browser-logs@0.3.4’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/config-loader@0.2.2’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/dev-server@0.2.5’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/test-runner-chrome@0.13.4’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/test-runner-commands@0.7.0’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/test-runner-core@0.11.6’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/test-runner-mocha@0.8.2’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/dev-server-rollup@0.5.4’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@rollup/plugin-node-resolve@15.2.3’,
npm WARN EBADENGINE required: { node: ‘>=14.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/dev-server-core@0.6.3’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘rollup@3.29.4’,
npm WARN EBADENGINE required: { node: ‘>=14.18.0’, npm: ‘>=8.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/test-runner-coverage-v8@0.7.3’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘puppeteer-core@19.11.1’,
npm WARN EBADENGINE required: { node: ‘>=14.14.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/dev-server-core@0.6.3’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/test-runner-core@0.12.0’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘lru-cache@8.0.5’,
npm WARN EBADENGINE required: { node: ‘>=16.14’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/test-runner-core@0.12.0’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘synckit@0.8.8’,
npm WARN EBADENGINE required: { node: ‘^14.18.0 || >=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/core@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/types@29.6.3’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-cli@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/console@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/reporters@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/test-result@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/transform@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-changed-files@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-config@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-haste-map@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-message-util@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-regex-util@29.6.3’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-resolve@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-resolve-dependencies@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-runner@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-runtime@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-snapshot@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-util@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-validate@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-watcher@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘pretty-format@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-worker@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/schemas@29.6.3’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘create-jest@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/test-sequencer@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘babel-jest@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-circus@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-environment-node@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-get-type@29.6.3’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘babel-preset-jest@29.6.3’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘babel-plugin-jest-hoist@29.6.3’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/environment@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/expect@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-each@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-matcher-utils@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/fake-timers@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-mock@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘expect@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/expect-utils@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-diff@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘diff-sequences@29.6.3’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-docblock@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-leak-detector@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/globals@29.7.0’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/source-map@29.6.3’,
npm WARN EBADENGINE required: { node: ‘^14.15.0 || ^16.10.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘commander@11.0.0’,
npm WARN EBADENGINE required: { node: ‘>=16’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘execa@7.2.0’,
npm WARN EBADENGINE required: { node: ‘^14.18.0 || ^16.14.0 || >=18.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘listr2@6.6.1’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘yaml@2.3.1’,
npm WARN EBADENGINE required: { node: ‘>= 14’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@puppeteer/browsers@0.5.0’,
npm WARN EBADENGINE required: { node: ‘>=14.1.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘pretty-bytes@6.1.1’,
npm WARN EBADENGINE required: { node: ‘^14.13.1 || >=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘workbox-build@7.0.0’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@webpack-cli/configtest@2.1.1’,
npm WARN EBADENGINE required: { node: ‘>=14.15.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@webpack-cli/info@2.0.2’,
npm WARN EBADENGINE required: { node: ‘>=14.15.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@webpack-cli/serve@2.0.5’,
npm WARN EBADENGINE required: { node: ‘>=14.15.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘commander@10.0.1’,
npm WARN EBADENGINE required: { node: ‘>=14’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘lru-cache@8.0.5’,
npm WARN EBADENGINE required: { node: ‘>=16.14’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘lru-cache@8.0.5’,
npm WARN EBADENGINE required: { node: ‘>=16.14’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/dev-server-core@0.6.3’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@web/dev-server-core@0.6.3’,
npm WARN EBADENGINE required: { node: ‘>=16.0.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘lru-cache@8.0.5’,
npm WARN EBADENGINE required: { node: ‘>=16.14’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘human-signals@4.3.1’,
npm WARN EBADENGINE required: { node: ‘>=14.18.0’ },
npm WARN EBADENGINE current: { node: ‘v12.22.9’, npm: ‘8.5.1’ }
npm WARN EBADENGINE }
npm WARN deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated workbox-google-analytics@7.0.0: It is not compatible with newer versions of GA starting with v4, as long as you are using GAv3 it should be ok, but the package is not longer being maintained
npm WARN deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated @babel/plugin-proposal-dynamic-import@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-dynamic-import instead.
npm WARN deprecated rollup-plugin-terser@7.0.2: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser

added 1580 packages, changed 1 package, and audited 1582 packages in 2m

203 packages are looking for funding
run npm fund for details

12 vulnerabilities (3 moderate, 9 high)

To address issues that do not require attention, run:
npm audit fix

To address all issues (including breaking changes), run:
npm audit fix --force

Run npm audit for details.
Success!

Snowbird · February 15, 2024, 9:38pm

OK! After much gnashing of teeth, I finally got

from the make run-preview-env command.

Now I have a question about the next instruction:

I’m unclear how I “ensure server is up and running”. If I was in VSCode I would use the Live Server plugin and get my site running in the browser that way. But I’m guessing that I need to do something on the Ubuntu side to get a web server running?

Snowbird · February 15, 2024, 9:58pm

OK. Some more progress and it might relate to starting “the server”.

My intention is to use VS Code on the Windows side for development. It appears that I have this setup correctly:

You can see in the lower left corner it indicates that I’m connected to Ubuntu through WSL. And when I hover over files it shows (I believe) the files on Ubuntu.

I’ve also got a terminal at the bottom that is (I believe) over on the Ubuntu side.

Does it look like I can go ahead and run the make load-data command?

Khemarato.bhikkhu · February 16, 2024, 3:42am

Congratulations! I say go for it! What’s the worst that could happen?? (Famous last words…)

Snowbird · February 16, 2024, 5:16am

Ok, well this was the worst this time:

Error response from daemon: Container ab5e6d7b18e4e7f359f0e69ed0125ca743fdce4cc23e87e6229f3e680f273aea is not running
make[1]: *** [Makefile:69: migrate] Error 1
make[1]: Leaving directory '/home/learning/suttacentral'
make: *** [Makefile:72: load-data] Error 2

Was I supposed to do something to start a Docker container?

To clarify, I’m getting VSCode up and running through to the Ubuntu side. The first command I run is make load-data. I tried it both in the Ubuntu terminal and in the VSCode terminal (with the Ubuntu prompt).

Ideas?

Khemarato.bhikkhu · February 16, 2024, 5:32am

Yes. You need to have a server running to load that sever up with data. Use the make run-... command above

Snowbird · February 16, 2024, 6:08am

Ah, so could that step 4 been called “Start server”? Cause that would have helped.

Because this time as soon as I ran in while in VSCode…

Tada!

Amazing. Thanks for all the help!

It seems to be working completely. Even the search.

Now I’m wondering what 1.2 Loading the data in the instructions above is supposed to do. In the terminal I ran make run-dev I don’t have a prompt. I guess I could run make load-data in a different terminal, but I’m not even sure why I need to when I have my very own site already up and running.

Khemarato.bhikkhu · February 16, 2024, 8:10am

Because that’s the terminal currently running the server

BethL · February 16, 2024, 1:26pm

Chuckles yes, Venerable, this is a vestigial response to what, in my past career, amounted to a house-on-fire due to the security risk (government-hosted, public-facing). As in, who let that SSL certificate expire? (Eyes squarely on me ). Which always led me to think, why do we have all these websites?

May your installation woes go away

Snowbird · February 16, 2024, 7:04pm

I’m wondering if we could backup and you or someone else could explain just what “Loading the data” means at that point in the instructions. I think I understand that indexing Arango has to happen because the Arango search has it’s own custom database and so without re-indexing it wouldn’t know about the changes.

But what is make load-data doing? I don’t see a file in the directory called load-data.