node-sqlite | SQLite client for Node.js applications | Data Migration library

Joshua Wise's (better-sqlite3's creator) answer over on GitHub:

Database connections are automatically closed when they are garbage collected, which is non-deterministic. If you want to know that the connection is closed (rather than guessing), you should call .close().

You can just open one database connection for the entire thread (the entire process if you're not using worker threads), and share that connection between every request. Node.js is single-threaded, so you don't have to worry about simultaneous access, even if multiple requests are being handled concurrently. The one caveat is that you should never have a SQLite transaction open across multiple ticks of the event loop (i.e., don't use await between BEGIN and COMMIT), because then other requests could accidentally inject SQL into your transactions. Also, SQLite transactions are serialized (you can't have more than one at a time), so you should open and close them as quickly as possible; keeping them open across ticks of the event loop is bad for performance.

https://pyproj4.github.io/pyproj/stable/installation.html

I would recommend either:

1. Upgrade to pip>=19 so PROJ 7.2 is in the wheel.
2. ENV PROJ_DIR=/path/to/proj/install and when you install PROJ: ./configure --prefix $PROJ_DIR

So, I created a sorting function to sort it right after running the query and getting the results. I reported this issue to the github repository. This is the sorting function.

Since you want to use async/await, and the node-sqlite3 (sqlite3) library does not support the Promise API, you need to use the node-sqlite (sqlite) library, which is a wrapper over sqlite3 and adds support for the Promise API. Then, your code will look something like this:

The issue I see in your code is, the console.log is outside of the callback function.