utils-merge | merge utility function | YAML Processing library

So in classic fashion, I've found the solution right after posting.

I removed "node": "^14.4.0" from my package.json and it successfully built.

Disclaimer: I work for Netlify

As we mentioned to you in your helpdesk ticket on this same topic, our deploy environment is very naked - you have to:

1. specify dependencies that we can automatically install - npm/yarn deps, bower deps, gems and python packages.
2. install other dependencies yourself. the 'dotnet' program will be one of this type. We don't have it in our install environment, so you need to somehow import a copy of it into the environment. Seems like you can download the entire SDK here: https://www.microsoft.com/net/download/linux and then you need to import ONLY what is necessary for your build - it will take a very long time to build your site if we have to download the entire SDK, so see what you can trim down to get 'dotnet' to run.

For the purposes of #2, you'll probably need to test things in our build environment. How to do that, and details you'll need about the build environment such as OS type so you can download the right version of the SDK are described in this article:

https://www.netlify.com/blog/2016/10/18/how-our-build-bots-build-sites/

This will take some work on your part. It will not be trivial. It is not something we can help with in more detail than that for free customers unless you come with specific questions and examples.

To address some thoughts in the comments:

• build.sh is indeed our build script
• 9:46:52 AM: /opt/build/build.sh: line 427: dotnet: command not found means that literally there is no dotnet command available to run - not that some config file is missing.
• we only try to run it once since you have set your command to use && to chain several commands - one fails, the whole chain fails, and we don't need to run it two more times once the first failure occurs :)

We do not have much information to work with (as the console output given by Node isn't very useful in this case), but it looks like NPM/Node messed something up while installing.

You stated that you've already tried to re-install Node. You should definitely also re-install NPM (This is a great tutorial to remove both completely: https://stackoverflow.com/a/20711410/10588376).

If you just forgot to mention that you also re-installed NPM and you already did it, I would recommend downgrading Node. You are running v12.4.0 which is the latest (not so stable) version of Node. You could download Node v10.16.0 (https://nodejs.org/en/), which is the LTS (Long Term Support) version of Node (LTS is the recommended version by Node).

As it seems downgrading solved the problem here: https://stackoverflow.com/a/56512076/10588376 (this is for Linux tho, but it could be worth a try on windows too)

Just like the warning said

DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

To avoid the depreciation warning. You need to find out the new Buffer() methods in your codes and replace them with a new one. Such as in the extend-node.js file(NodeTaskApp-master\node_modules\iconv-lite\lib), Line 13:

I had the same issue today and indeed not encouraging to have warnings on a fresh new project. I just add babel core manually yarn add babel-core@^6.0.0and did not had pbs to run the new app.

1. npm WARN No repository field:

   This is a warning message telling you that the package.json file doesn't have a defined repository. This really should be defined, but won't adversely affect the run of your program.

2. COSMIC_BUCKET=your-bucket-slug npm start COSMIC_BUCKET=your-bucket-slug sets an environment variable called COSMIC_BUCKET equal to the value your-bucket-slug. This is a runtime variable for CosmicJS. npm start runs a command which starts the web application.

I was able to build and run my project following the instructions here.

More specifically:

If I import HyperHTMLElement from 'hyperhtml-element' then I get raw es6 in my bundle.

Which is exactly what should happen, right ? You are using ES6 syntax, you get it.

But here you are bundling with browserify, which AFAIK doesn't even understand ES6, only CommonJS.

Accordingly, if you want to require HyperHTMLElement for CommonJS you have to be a bit more specific:

After a lot of persistence, finally found the solution so answering my own question:

If your stack is heroku-16, these are the Heroku buildpacks you want to add (in this particular order!):

• https://github.com/Starkast/heroku-buildpack-cmake.git
• https://github.com/onboardiq/heroku16-buildpack-opencv3.git
• heroku/nodejs