y18n | : ledger : the bare-bones i18n library used by yargs | Build Tool library

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 :)

try installing react-native-material-design locally instead of globally.

It looks like react-native-material-design depends on react-native-material-design-styles which won't be packaged by React Native's bundler since its parent is a global module.

I figured it out (mostly). Due to some magic that I haven't yet sorted out, I got a reference to npm inserted into my packages.json file.

Here's what I think happened: When I ran yarn list it informed me that a newer version of yarn was available. After considerable struggling and Googling, I figured out that I could upgrade yarn and npm to the latest version via:

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.

The following installed the Terminalizer (adding the --unsafe-perm flag) (please pitch in if there's a better solution. I am no expert in npm):

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

More specifically:

I recommend that you try install y18n first then upgrade npm like this:

We're not supporting Node 4 anymore — try upgrading to Node 8 & NPM 5 and it should be smooth sailing!

This looks like a known issue when you install watchman using npm. It can be fixed by removing watchman installed using npm and installing it using homebrew.