/AirportCode/?select(iata,airport,latitude,longitude)&country_code=US&sort(+iata)
Using harperdb-nextjs dev
to run the script, the env variables are not available:
import dotenv from 'dotenv';
dotenv.config();
console.log(process.env);
I believe this is related to the @harperdb/nextjs
extension since the process is started from the /app
directory. Copied
the .env
file to /app
as a workaround.
Dev mode with harperdb-nextjs dev
works, but HDB CLI is executed with harperdb run .
and therefore doesn't watch for changes (e.g. the resources.js
file is not reloaded).
Attempted HARPERDB_NEXTJS_MODE=dev harperdb dev .
but this appears to infinitely
reload due to changes in the .next
directory.
With the Next app in the root directory, MQTT client is unable to establish a connection, perhaps of how the @harperdb/nextjs
extension is configured? APp is now located under /app
.
Attempted to use request.login
as a means to track sessions, but received exception of request is not defined
.
https://docs.harperdb.io/docs/developers/applications/web-applications#cookie-support
Occasionally, trying to hit http://localhost:9926/app
will result in a Not found
response, indicating that the
request isn't being handled by the Next.js extension. Neither stopping HDB nor killing the processes on port 9926
seemed to resolve the issue. pkill -f node
also didn't work. Full restart of the system resolved the issue.
When the start is successful, I see Debugger listening on ws://127.0.0.1:9229
in the terminal. When it fails, I
get an error that the address is already in use.