async.js | composable way to manipulate sequences | Reactive Programming library

ModuleNotFoundError: Module not found: Error: Can't resolve '@popperjs/core' suggests that you need to install @popperjs/core.

In case anyone comes to this error. Even configuring the proxy at server and container level didn't worked. I'd found out that Jenkins has a proxy configuration at the application level. So I went into Jenkins, Administration section and configured the proxy properly. After that was done, it all started to work.

First, in webpack.mix.js, do you need the SASS line? Because it's causing issues.

I think the problem is that your package.json says you are using ES6 modules, but your Babel config is using module.exports which is CommonJS (not ES6 modules).

I renamed my babel.config.js to babel.config.cjs and this fixed the problem. I guess you could also change module.exports to export default but I haven't tried this.

Recall that handleAsync doesn't execute the handler - it only creates the middleware. You're also expecting it to not throw, but rather to pass the error on via the next callback. That's the reason you're using a middleware like this - so you can have async route handlers and have any possible errors be passed automatically to next so that the errors get passed to your error handler.

You can test whether it actually catches a promise rejection from a wrapped route handler. Here's an example, which I haven't had the chance to test:

There are two major reasons for this cause.

1. Setting enableDangerousExperimentalLeanBuils to true.
2. Missing expo-splash-screen package.

The error is because it's(Gradle build) looking for expo-modules-splashscreen package, which is supposedly moved out of expo's main module in SDK 41, hence needs to be separately installed. In order to fix this, there are two workarounds:

1. Remove enableDangerousExperimentalLeanBuilds property. (Not tested)
2. Install expo-splash-screen using npm install expo-splash-screen.(Tested and working)

This is because you use function(cb) instead of (cb)=>{}. If you try console logging this, you will see that this is the function. This has to do with scoping. https://www.w3schools.com/js/js_scope.asp will give you some more info. Another place with some more information: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/this

Where are your app stylesheets located? I think your clue is here:

ModuleNotFoundError: Module not found: Error: Can't resolve 'stylesheets/application' in '/tmp/build_44a69be4/app/javascript/packs'

Webpacker is looking for 'stylesheets/application.scss' in the /app/javascript/packs directory and can't find it.

I've managed to fix it with this hook: