Im having issues getting a parceljs production build to pass successfully on goCd pipeline.

In the package.json I have this:

"scripts": {
    "dev": "parcel src/index.html",
    "production": "parcel build src/index.html --no-source-maps"
 },

If I run npm run production locally, it seems to build fine (except for a warning) with the following output:

dist/index.html                 380 B    435ms
dist/index.6e3474c2.js    ⚠️  1.01 MB    9.94s

Now on goCd, we have a PR pipeline which does a npm install and a npm run production. This is the output:

Building...
Bundling...
Packaging & Optimizing...
✨ Built in 46.93s

dist/index.html                 380 B    25.91s
dist/index.c65c67b3.js    ⚠️  1.02 MB    25.82s
78
[go] Task status: failed, took: 50.325s, exited: 139
[go] Task status: passed, took: 0.973s
[go] Current job status: failed 

So as you can see, the task to bundle and package seems to have gone successfully but goCD has failed the job.

My first query is what causes the ParcelJS warning? Is it the fact that index.js is over 1mb? I can't seem to find any documentation on it...

Second is whether the goCd failure could have resulted because the warning is present? However, I can't seem to find anything in the docs to suggest this: https://docs.gocd.org/21.1.0/advanced_usage/dev_conditional_task_execution.html

Thanks