url-exists | A simple node library to determine if a url exists | Runtime Evironment library

urlExists is a callback-based function, you can promisify it and then await it.

To promisify urlExists function, you can use built-in node module: util.promisify.

Unless the ftp is open and no authentication is needed. I’d recommend to use some npm package for communicating with the ftp server. Actually even is no auth is needed you moght have to establish a connection to the server.

Like suggested by Lawrence Cherone above. Most modern FTP servers supprr some HTTP integration and changing the URL protocol prefix from FTP to HTTP(S) should do the trick

Checkout - this post - Node.js connect to ftp and download files which recommends this package https://github.com/mscdex/node-ftp

Establish a connection and use the available API to search for the file.

Lastly I’d recommend to read the post about the difference between FTP and HTTP(S) protocols Access FTP via HTTP?

You can make use of Promises here. First, you can .map() your array of URLs to an array of Promises which either reject or resolve depending on whether calling urlExists errors or not for a given URL.

Once you have an array of promises, you can pass that into a call to Promise.all() which will return a new promise. When this promise resolves, it will contain an array of the form [[url1, existsStatus1], ...], which you can then use .find() on to find the first occurrence where existsStatus is true:

In short, you can't.

You can't force an async request to be synchronous.

You have a couple different syntactical approaches (Promises, async/await, events via Node.js http, callbacks, etc), but it's all going to boil down to being async in some way.

The async/await pattern will look the most synchronous, but it will still be async.

The package you're using specifically uses the callback pattern, so you'll need to adjust your other code to be async. You can mix and match these approaches.

My personal preference is to wrap non-Promise patterns into a Promise pattern, then use async/await syntax throughout. Again, this look synchronous, but keep in mind it isn't and deal with it accordingly.

You can wrap callback syntax as a Promise like this:

All the code inside the evaluate is executed on the chromium side.
As urlExists is being imported on the node side, you wouldn't be able to access to that function from the browser.

Unless you expose it using page.exposeFunction. Once you expose that function, chromium will be able to call urlExists.

How about

1) adding an extra field status in the table and set as 'false' for page which gets deleted.

2) Redirect to the URL only for page which has active status or redirect it to a fallback URL.

to handle url with error you can use this

Someone reported same problem in this issue and his case was similar to yours. As discussed in comments, this worked for you, so I am posting this as answer also:

It sounds like it's trying to load a native extension that wasn't compiled for linux (in the container) -- maybe you previously installed the extension on OS X and it's trying to load that binary. If you mean this is a node app, try just removing node_modules and run npm install again