type-detect | Improved typeof detection for nodejs and the browser | Runtime Evironment library

Travis CI keeps a cache of your vendor folder in order to make builds run quicker (and reduce unnecessary traffic for them). If you've made some changes to your composer.lock file Travis CI may need to update the files stored in the vendor folder.

Other times it won't need to do this, and so will have a shorter build time.

You are not using ngOnChanges the right way, its going to be triggered everytime your input change no matter what the value is which means you need to check if that value is what you expect it to be with SimpleChanges.

This seems to be a problem with the virtual box filesystem. I created an issue to composer and hopefully more insight will be gained.

https://github.com/composer/package-versions-deprecated/issues/21

I used this and It works for me.

Looks like composer 1.10.11 is broken. You can switch to 1.10.10 like this:

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

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

If you specify https then that will be looking for a login user and password I believe, which I don't think it can load automatically. I would list it simply as "user/repo" and make sure that machine has an ssh key on it that is in github like the setup described in help such as https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#platform-linux and that things are setup so that pulling down that repo does not require user interaction.

EDIT: After testing, I think the issue is that your name in the package.json does not match how you have listed it in your main project's dependencies. In my test, this resulted in the modules being installed but I got the extraneous message.