serialize-javascript | Serialize JavaScript to a superset of JSON | Runtime Evironment library

I found the issue, it was actually because I had a chrome extension installed that would overwrite the Time zone for this specific site on localhost for some reason. The way that it works, was by overriding the Date class. I fixed the issue, by uninstalling/disabling the extension.

Thanks for your help everyone!

Unless resorting to hacks like posting to a dummy target, AJAX is the way to go.

This works:

From https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities

To find the package that must be updated, check the “Path” field for the location of the package with the vulnerability, then check for the package that depends on it. For example, if the path to the vulnerability is @package-name > dependent-package > package-with-vulnerability, you will need to update dependent-package.

It looks that you need to update https://www.npmjs.com/package/copy-webpack-plugin

If your build takes longer than 10m without output this will happen.

You can use travis_wait to print something to the console each minute, as per the docs: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received

Just travis_wait {your_command} and you should be good to go.

Be aware that your build taking longer than 10m could be a indicator of a more complicated underlying problem/freeze.

It seems in this case the error shows because the version of ts-node being used does not support ES Module syntax, as is being discussed here. I found out from that ticket that ts-node v8.10.0 provides experimental support, so maybe updating it will get this working. I don't know of any other solutions, but you should be able to run the files by compiling the .ts to .js and run them with node instead of ts-node. Let me know otherwise, I'm happy to dig a little further.

I was able to figure it out. I am not sure that I completely understand what's going on. I'll have to continue playing with it in order to fully grasp what's going on. Here is what my webpack.config.js file look like now.

Try deleting your Gradle folder c:\users\**username**\.gradle In our experience we have seen this issue and clearing the Gradle folder with it's caches has solved it sometimes.

Take a look at the package.json. The plugin has a dependency of "serialize-javascript": "^1.7.0" and caret range means that <2.0.0 will be downloaded, actually the last acceptable available version is 1.9.1, where the fix isn't presented.

Because the repository now is archived (considered deprecated), you could patch it by yourself or if it's possible to switch to the terser-webpack-plugin how documentation suggests.