DEV Community

Discussion on: Error: [nodemon] app crashed - waiting for file changes before starting...

garretharp profile image
Garret • Edited on

From the original error message, the log in the first request was made "replace transaction pool map on a sync with {}" which means the second request is the issue.

The API response from /api/transaction-pool-map is giving an HTML document rather than a JSON response. You will need to see what exactly the issue is on the API side of this.

However, also for the fact that you do not want your app to error out like that on users, you should also surround the JSON parse code with try-catch or create a new function that safely parses JSON without crashing.

For example a safe parse might be:

function safeParse (data) {
  try {
    const result = JSON.parse(data);
    return result; // Success valid JSON
  } catch (e) {
    console.error('JSON data error', data, e)
    return undefined; // Data was not valid JSON
Thread Thread
hafizsaifullah profile image
Hafiz Saifullah Author

When I run only one instance of app, either by using npm run dev or by using npm run dev-peer, it works fine. but when I try to run a second instance, app is crashed.
Is there may be an issue with installation or use of "cross-env"???