UglifyJS | JavaScript parser / mangler / compressor / beautifier | Runtime Evironment library

I'm trying to use the following code:

@apply w-[calc(theme(width.1/3)_-_1rem)] which according to the docs, should work. But every time I try and compile the code I get the following error:

So i'm new in JS and i have a task for mastering Ajax Requests.I should send an email input from form to the server and a lot more,but i can not figure out how to send this data to a server that is in another folder.I lost all my nerves with this task and i dont know what to do. So,i have a folder personal-website-server and another folder src where is my project,both folders are in another folder,the parent. It looks like this :
./
dist < webpack bundle folder
node_modules
personal-website-server
/ package.json in personal-website-server
src
and package.json in the parent folder Image for more understanding:

So,i should do this:
Upon clicking on the "Subscribe" button, implement the functionality for sending a user email to the server. For that, make POST Ajax request using http://localhost:3000/subscribe endpoint. The call to the server should only be made when the form is valid (the validate function )
The connection is made through a proxy to the server,idk how this thing works and i get it hard to do this task because its not so described.
Codes:
I created fetch.js in src that checks if email is valid and sends it to the server,like i understood:

We are using create-react-app and Typescript within all of our projects and a slightly large module of commonly used React components has emerged. Trying to factor these out into its own NPM package (for easier maintenance and better reuse), here called PackageA, we have arrived at a situation where the overall size of a test app, here called TestApp, is larger than it was before (when the same code existed inside the code base of the same app). TestApp is a VERY rudimentary app which basically just showcases some (but not all) parts of the components in PackageA, formerly with the components inside the project itself, and now with this part removed and instead imported from privately published PackageA.

Sizes of initial JS chunks before factoring out PackageA with components from TestApp ("main" is assumed to be code from the project itself and the other chunk is believed to hold dependencies):

• Gzipped: "main" chunk ~ 31 kB, chunk with external dependencies ~ 193 kB (from output after building the app)
• Unzipped: "main" chunk ~ 93 kB, chunk with external dependencies ~ 653 kB (from browser)

Sizes after factoring out PackageA from TestApp:

• Gzipped: main chunk ~ 22 kB, chunk with external dependencies ~ 215 kB (from output after building the app)
• Unzipped: main chunk ~ 57 kB, chunk with external dependencies ~ 745 kB (from browser)

As can be seen, the overall size increases with 13 kB gzipped and 56 kB unzipped. This corresponds to an increase of ~ 6% gzipped and ~ 8% unzipped. This is not insanely much but I would still expect them to be somewhat similar.

• The contents of PackageA is published as es6 modules to allow for tree-shaking which seem to work properly since unused parts of PackageA are not emitted into the output chunks of TestApp.
• Minification of PackageA is done by UglifyJS prior to publishing using both --compress and --mangle options.
• Source maps are not included in the source files of PackageA but only available separately.
• The only packages listed under dependencies in PackageA's package.json are NOT used anywhere else in TestApp and were subsequently removed from the TestApp's package.json at the same time as they were added to PackageA's package.json. The same versions were used. All other dependencies of PackageA are listed under peerDependencies.
• All sizes were verified after deleting the node_modules folder and running a fresh install of dependencies.
• The contents of PackageA is exactly the same as the deleted folder from TestApp with the exception of an added index.ts page which exports the contents of the other files. This file is < 3 kB unzipped in size.

What could be possible sources of this increase in size and where could we start looking? Perhaps this increase might lie in how the code is transpiled in the package and that create-react-app is somehow able to do this more efficiently for code included in the project itself than for imported code. I know this is a tough question that might have many answers and that is hard to reply to.

This is the tsconfig.json used in the factored out PackageA:

I am having MVC application and trying to add Bootsrap5 through Webpack and am getting following error. I have tried many of the workaround with stage-0, stage-2 and stage-3 but nothing worked for me.

I am suspecting the issue is because of three dots (Spread syntax) but the workaround not helped for me.

Issue:

In running yarn run build I am running into the following error:

I have a typescript react project where I try to add the react-refresh-webpack-client and get this error:

my webpack config:

Please could someone shed some light into the issues I'm having with Webpack. I've not used Webpack for fonts before and have run into a bit of a headache I've not been able to solve. I'm pulling the fonts from a .css file using url().

What I'm getting after Webpack has done its thing is 3 .woff files with their names changed to a hash like name. I then have a fonts folder with the 3 fonts in named correctly. Looking at the main.css (the one Webpack produced) the url() is now looking at the font files with the hash names. When I open the hash named .woff files its an export command pointing to the fonts folder and to the correct font.... Is this how it meant to work?

When I load up the webpack in the console I have errors for each file: Failed to decode downloaded font: http://localhost/OPM/wpcontent/themes/theme/assets/build/b4f8bd69b3d37cc51e2b.woff OTS parsing error: invalid sfntVersion: 1702391919

This is wants in the .woff file export default __webpack_public_path__ + "fonts/font-icons.woff";

I am attempting to add an additional functionality to the Divi WordPress theme. To do this, I am trying to build an extension to the theme and then a custom module within the extension. Elegant Themes, the developer of Divi, provides a tutorial for creating an extension and also for creating a module within the extension.

My development PC is running XAMPP over Ubuntu 20.04. I followed the tutorials and installed WordPress + Divi. I then installed Node.js by running sudo apt install node and then installed npm by running sudo apt install npm. Next, I ran sudo npm install -g yarn to install Yarn.

The next step called for me to navigate to the plugins folder (/opt/lampp/htdocs/development/wp-content/plugins) of my WordPress site and run npx create-divi-extension development-1.

When I attempted to run this command, I received the following response:

I have created a simple MERN stack application and tried to deploy the app on heroku however, the build fails with this error: