Can't run this: Error: Command failed: node npm run i18n:extract and Cannot find module 'fs.realpath/index.js'

[osseonews]

Error while starting AdminForth. Set it up with instructions. using NPM. Database connects fine.

Node.js version:
v24.14.0

Error:

Error: Command failed: node npm run i18n:extract

spa@0.0.0 i18n:extract
echo {} > i18n-empty.json && vue-i18n-extract report --vueFiles "./src/**/*.{js,vue,ts}" --output ./i18n-messages.json --languageFiles "i18n-empty.json" --add

node:internal/modules/cjs/loader:539
throw err;
^

Error: Cannot find module 'fs.realpath/index.js'. Please verify that the package.json has a valid "main" entry

at Object.<anonymous> (node_modules/vue-i18n-extract/node_modules/glob/glob.js:43:10)

{
code: 'MODULE_NOT_FOUND',
requestPath: 'fs.realpath'
}

Node.js v24.14.0

[osseonews]

We deleted the package-lock and node modules and did npm install again and it worked. I am guessing it's better to not use npm on the initial install?

[yaroslav8765]

Hi! Thanks for your report!
We will try to reproduce it and fix, if problem exists

[osseonews]

Thanks. BTW, do you know how to deploy this on Digital Ocean app platform? We keep trying and it fails. What is the proper run and build command. We are not using a docker file because we tried that also and it failed. Thanks.

[yaroslav8765]

Thanks. BTW, do you know how to deploy this on Digital Ocean app platform? We keep trying and it fails. What is the proper run and build command. We are not using a docker file because we tried that also and it failed. Thanks.

We recommend to use docker for deploy. Can you please provide an error message, so we can help with that

[osseonews]

The error is that it can't find some python library to install? Which is strange because it's a node app. Also, i think it is trying to install SQLLite, but we use postgres? I'm not really sure as I didn't undewrstand the error and it just would not build with the docker file. You can test on the Digital Ocean App platform and probably be better able to diagnose the issue. BTW, locally it works fine. Just can't deploy it.

[osseonews]

I there is an issue with this also in the package.json: "_env:prod": "dotenvx run -f .env.prod --"

This requires dotenvx to run in production and the then the DATABASEURL is from the .env.prod? This won't work on most platforms. The ENV value comes from the ENV value in the platform ENV manager. We don't use .env.prod in production. Plus I noticed that you don't .gitignore this env.prod file, so it goes unecrypted into our git which is really risky. I've used dotenvx before and I like it, but there are no instructions here on how to encrypt the files, plus this won't work in something like Digital OCean, as they handle the ENV directly on the platform.

[osseonews]

Here is the exact error in Digital Ocean when trying to deploy to their app platform using the docker file:

Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python --python was not set on the command line
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python Python is not set from environment variable PYTHON
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python checking if "python3" can be used
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python - executable path is ""
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python - "" could not be run
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python checking if "python" can be used
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python - executable path is ""
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python - "" could not be run
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python 
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python **********************************************************
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python You need to install the latest version of Python.
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python you can try one of the following options:
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python - Use the switch --python="/path/to/pythonexecutable"
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python (accepted by both node-gyp and npm)
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python - Set the environment variable PYTHON
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python For more information consult the documentation at:
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python **********************************************************
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! find Python 
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! configure error 
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! stack Error: Could not find any Python installation to use
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! stack at PythonFinder.fail (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:300:11)
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! stack at PythonFinder.findPython (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:160:17)
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! stack at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! stack at async configure (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:27:18)
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! stack at async run (/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js:81:18)
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! System Linux 5.15.63
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--release"
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! cwd /code/node_modules/better-sqlite3
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! node -v v24.16.0
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! node-gyp -v v12.3.0
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! $npm_package_name better-sqlite3
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! $npm_package_version 11.10.0
Jun 11 18:36:27  �[34m│�[0m npm error gyp ERR! not ok

[ivictbor]

This requires dotenvx to run in production and the then the DATABASEURL is from the .env.prod?

Not exactly.

If you created files with recent version of adminforth CLI - they have comments on top explaining what to put there.

.env.prod and .env.local only for non-sensitive (non-secret) values. Like public constants which are safe to commit to production, not passwords, not secrets, not tokens.
.env is .gitignored so for local development you can put values there.

.env.local might have your local database URL which you specified in CLI. Most of local dev databases are not sensitive so we suggest it in .env.local as default. If you specify some non localhost address - CLI should put it to .env cause it assumes it might be sensitive

For production, such sensitive variables as DATABSE_URL - you should deliver them from natural system env, from services what u use/ or docker env or anything. So .env will not be used in prod. And .env.prod - is just a handy way to keep some fixed public constants which are production specific e.g. ENV=prod <- this is not so secret. When such constants set up in repo there is less risk for DevOps to not set them in system env, and for devs it is more clear. Though you might ignore it - and just keep empty.

[osseonews]

right but when you run the install steps, adminforth adds the databaseurl to the .env.prod. At least that's what happened to us. anyway, printed the errors above. Not sure why there is an attempt to install sqllite automatically if we are using postgres as the database, and maybe that's why the python lib is required? how can we ignore the sqllite if that's the issue?

[ivictbor]

right but when you run the install steps, adminforth adds the database url to the .env.prod

Interesting. We will check this. Just to clarify did you use a) postgresql://user:pass@localhost or b) postgresql://user:pass@127.0.0.1 or c) postgresql://user:pass@somedomain.com? This can help us to reproduce. Just to understand a/b or c?

Not sure why there is an attempt to install sqllite automatically if we are using postgres

Yep, you are right here and this is in our roadmap already: unfortunately for now all database connectors are bundled, including their drivers are bundled inside so you can add many different database types out of the box. I think we will rework it very soon. For now yes, you need correct python version to make node-gyp work. This is standard pain for many node modules - but you can easily check how to deal with nodegyp.

[osseonews]

1. Option C (we use Neon for postgres database)
2. nodegyp: I'm not sure how to deal with it. how do we install the correct python version if this is a node app? We have never had this issue with other node apps, so we are not sure how to deal with it. Thanks.

[osseonews]

OK, so I used AI and it recommended to add the code below to the docker file, and it worked on Digital Ocean. You might want to add this to your docs:

# Install standard Python 3 and C++ compiler tools required by better-sqlite3
RUN apt-get update && apt-get install -y python3 make g++ && rm -rf /var/lib/apt/lists/*
# Inform node-gyp exactly where Python 3 is located
ENV PYTHON=/usr/bin/python3

Also, there is a conflict with the docker file and installed package.json. The package.json when you install is missing, migrate:prod, so this throws an error. We added the code below for migrate:prod to package.json (we don't use migrations actually as we have another backend doing that, but it's required). And it worked. You might want to add this also to the docs. Anyone who uses migrations, will obviously need to put them there.

"migrate:prod": "echo 'No database migrations configured'",

Finally, Digitial Ocean runs on port 8080, but yours runs on 3500, so this needs to be updated in the Digital Ocean settings to use port 3500 (it's in their app settings).

[osseonews]

Actually, I spoke too soon, as the the code builds now with the above, but the API routes all return 500. Like below for the Login API. Any ideas about this? Why would this happen? it built fine.

app/adminapi/v1/login
Request MethodPOST
Status Code 500 Internal Server Error

[osseonews]

What's strange about this error, is that the API works fine if you type in the wrong username and password. It hits the API and correctly returns unauthorized. But, when you type in the right information, we get a 500 error and other errrors like below in the console:

index-D9O4SvQL.js:2 error in callApi /adminapi/v1/login SyntaxError: Unexpected token 'I', "Internal s"... is not valid JSON
wt @ index-D9O4SvQL.js:2
await in wt
O @ index-D9O4SvQL.js:2
I @ LoginView-7PF8Gr1i.js:1
Bt @ @vue-aKgBuYAB.js:16
Ne @ @vue-aKgBuYAB.js:16
n @ @vue-aKgBuYAB.js:24Understand this error
@vue-aKgBuYAB.js:15 [Vue warn]: Unhandled error during execution of native event handler 
  at <Button onClick=fn<I> loader=true disabled=true  ... > 
  at <LoginView onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< Proxy(Object) {__v_skip: true} > > 
  at <RouterView> 
  at <App>
v @ @vue-aKgBuYAB.js:15
ac @ @vue-aKgBuYAB.js:16
Kt @ @vue-aKgBuYAB.js:16
(anonymous) @ @vue-aKgBuYAB.js:16
Promise.catch
Ne @ @vue-aKgBuYAB.js:16
n @ @vue-aKgBuYAB.js:24Understand this warning
LoginView-7PF8Gr1i.js:1 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'error')
    at I (LoginView-7PF8Gr1i.js:1:2441)

[yaroslav8765]

Hi!

If this is possible, can you please provide a log from the container, so we can see error details.
( I think, that there might be no connection to the database, so it crushes. But, this is just a guess)