js-tokens | Tiny JavaScript tokenizer | Regex 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 :)

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.

Can you update your package.json file with below:

Do you want to check if you are logged into npm using npm whoami?

I just ran that and noticed I was logged out. Logging back in fixed the issue. Before I logged into, I could download all packages without the scope namespaces ie I couldn't download @babel/pkg-name, @expo/pkg-name etc.

The problem was:"rootDir": "" in the configuration file.

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

More specifically:

A very detailed explanation was posted on this thread (asking much the same question). Thank you, Rhys Arkins!

https://github.com/npm/npm/issues/20434#issuecomment-402988364

This error is from webpack, you are mixing the loader syntax from webpack (1 and 2) in your shared config with the loader syntax from webpack 3 generated by scalajs-bundler.

https://webpack.js.org/migrate/3/#module-loaders-is-now-module-rules

You can upgrade your shared config: webpack.config.shared.js

So searched a bit further (didn't search well enough, apparently).

1. Syntax js-tokens;[3.0.0,4),[4.0.0,5) means larger than or equal of 3.0.0 but below 4 or larger than or equal of 4.0.0 but below 5, two sets, I think. Someone else can clarify, but that's what I got from https://maven.apache.org/enforcer/enforcer-rules/versionRanges.html :)

2. Maven Version Range Sets in Transitives Do Not Work. This can be handled currently with this

   dependencyOverrides += "org.webjars.npm" % "js-tokens" % "3.0.2"