gulp-uglify | Minify files with UglifyJS

I solved my problem, it turned out that I accidentally remove my nodemon package from package.json, and I had bad docker compose config. I changed it to this version:

I've figured it out. In my lib.ts I had to change the way I export my class:

gulp-sass 4.1.0 uses node-sass 4, and node-sass 4 does not support Node.js 16, as indicated in this table.

To support Node.js 16, upgrade gulp-sass: the latest version today is 5.1.0:

I believe that you don't need to import separate parts of the Swiper if you are using the bundled build of Swiper. So, just try the same code without import statements and Swiper.use statement.

Also, don't forget that in the default initialization, it might be helpful to enqueue the Swiper style file to have a default appearance.

If you want to use only the required parts of Swiper, you should include the source file in your source files, not just enqueueing the already built file that is located in the Generatepress.

In copy:css you have this line:

paths.src.base + '/assets/css/argon.css'

where apparently your error is. The problem is your paths.src.base is defined as

base: './' to which you are adding /assets/css/argon.css so you end up with

.//assets/css/argon.css note the two leading backslashes.

Get rid of the leading backslash in the /assets/... and check the rest of your code for the same problem.

Also since you are using gulp4 get rid of runSequence - look at the documentation for gulp.series.

Use the babel transform vue tag to es2015 can solve the problem. you need install the dependency:

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 could see pretty-checkbox's developer last published 4 years ago.

Let's say the new module used popper-js@2.0 and someone who already had popper-js@4.0 as direct or sub-dependency in their project is more likely to face unmet peer dependency on using the new module.

Downgrading the version is not recommended due to possible conflict with other modules. A workaround would be to add resolutions.

Before doing anything, ensure there is no other version of react installed globally, delete your node-modules folder and package-lock.json file. Ensure your package.json dependency has react@15.4.0 and only add popperjs@^1.16.0 if you're sure that other modules in your project are not relying on later versions of popperjs.

Take a look at this article for a good explanation on peer dependencies

If there are other modules that needs other versions of popperjs then in your package.json you could add an additional property at the end like below,

Turns out I'm an idiot and Watchify is "practically a must" since it caches dependencies between watched builds. Using a native gulp watch was my problem.

Updated gulpfile.js