base64-js | A polyfill for base64 functions atob and btoa | User Interface library

You should edit /www/js/index.js.

The other two files are created during the build process. A built Cordova app will have all www folder contents inside an android app structure, that's why they are inside /platforms/android/app/src/main/

The other index.js files are there because it's a Node.js pattern

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

Turns out that running the following command fixes the issue.

Solved it by updating and adding some node packages.

package.json

For the flat task try:

npm list |awk '{print $NF}'|tr "\n" ","

For the view task:

for package in $(npm list |awk '{print $NF}') do npm view $package done

Publish:

for package in $(npm list |awk '{print $NF}') do npm publish $package done

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.

I believe you are using cli built-in bundler (I wrote it), not webpack.

Yes, nodejs global var global is currently not supported. Also nodejs global vars process and Buffer have similar issues.

The cli doc has a patch to support process and Buffer.

Base64 is just an encoding which does not necessarily have anything to do with images. If you just need a placeholder i would recommend not adding the image until it is loaded and display a sized div instead.

If you really need to have an image there you can just make the source an SVG, which you do not even need to encode to Base64, because its data is already text. So it looks something like this:

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

More specifically: