gulp-babel | Gulp plugin for Babel | Plugin library

It seems like you could be missing a build step where you transform your code to be browser compatible. The require method is not available in the browser.

You have to use a tool which transforms your code so that it can be ran in the browser. One such tool is Browserify, another is rollup, and there may be more. These tools, generally speaking, bundle dependency sources in conjunction with your application code, which allows require statements to be transformed into some other pattern the browser does understand.

You can think of it like this (example is simplified):

Code written by you

I have FOUND this helpfull for migration to Gulp@4.0.0

https://www.sitepoint.com/how-to-migrate-to-gulp-4/

After a lot of researching, I found this blog which has the answer, or almost it has the links to the answer.

One of the links took me to the most detailed tutorial about Gulp + Browserify + Babelify it could ever exist. Here the link. These are a serie of tutorial explaining how to implement Gulp from Scratch. If you don't want to see the videos and just want the code go here.

This is my final gulpfile.js.

And this is the answer to my question:

My formerly build function in gulpfile.js (now called js)

I have had good success with promise-polyfill. As long as that loads before your promise-specific code, it should just work. I know that's not babel-specific, but it solved my IE-compatibility woes back when I still had to support IE.

For anyone who stumbles across this issue in the future (probably unlikely).

It turns out the culprit was the CDN being used in our production environment. I figured out that the bundle.js file I was uploading wasn't the same as was being served up in the site, and turned the CDN off which seemed to fix the issue. :/

The version of node and npm seem to be very old. I have been running nightwatch tests using selenium on travis, azure devops and github actions. My advice is to have the configuration through a yml file which is very simple. You can see mine in the below link and try it.

Reference: https://github.com/spnraju/nightwatchjs-selenium-example/blob/master/azure-pipelines.yml

It is almost certainly your use of the chokidar watch functionality. Your code won't even run for me. And you don't need that complexity. I suggest getting rid of

As per my comment to your question

This seems to be a TypeScript version problem, but the version in your package.json seems to be correct. Have you tried to run this from a script within your package.json, in stead of through your terminal?