eslint-import-resolver-babel-module | Custom eslint resolve for | Plugin library

I've been asked to go through our application and update all the frameworks as it was incredibly outdated, one of the things was to update babel, now one of our scripts in package.json was:

I am migrating a NodeJS project to Typescript. I have already created the configurations and it runs with only JS. I am using @babel/node to run it in a dev environment, but when I try to import a TS file into JS it doesn't work.

It throws the following error:

I am trying to add redux with redux toolkit to an existing react native app with my first attempt at atomic design.

I have wrapped my index.js components in a per the docs but it seems like react-redux is searching for a location called 'src/redux' which is throwing an error.

I originally tried to combine all redux functionality within an 'src/redux' folder and used jsonconfig.json to alias '_redux' to path 'src/redux' with subfolders and index.js files pointing to subfolders 'actions', 'reducers' and 'store'.

I came across some errors and figured it was probably bad form to have a folder called 'redux' so I changed it to 'appRedux' and then this problem appeared.

I've dropped node_modules and reinstalled multiple times, cleared metro caches, searched for any reference to 'src/redux' across the app, and finally started again from scratch by resetting git to HEAD and adding appRedux and new modules again, only to encounter the same error. Now I'm guessing that perhaps the folder naming issue was only a coincidence, but I'm at a loss on how to resolve.

Any pointers? There is not much out there on redux-toolkit with react native and I'd prefer not to have to write all the boilerplate redux code.

Full error:

I have an expo RN app that I was able to successfully upload to TestFlight last month but now is being rejected because of the AppStore's depreciation of the UIWebView version. I have removed all references of UIWebView, I have cleared the cache, I have refreshed the package-lock.json and even force removed all references with grep -r "UIWebView" . command. Nothing is working. Every time I rebuild my iOs app with Expo and then upload to TestFlight the build fails and throws this generic unhelpful error: This build is invalid.

I get an email with the below slightly more helpful message:

TMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. Learn more

I found one article saying I need to update my expo SDK version to 37 but when I do this my app breaks because I am on an old react native version (v 0.59) and they are not compatible.

I would really hate to rip apart my app, update the RN version, update the expo SDK version to only have the error persist.

Is there a way to get my app on App Store Connect without having to update my RN and expo SDK version in my app.json?

docs I have already looked through: ITMS-90809: Deprecated API Usage -- Apple will stop accepting submissions of apps that use UIWebView APIs https://developer.apple.com/documentation/uikit/uiwebview

app.json

We developed with expo and needed an eject so We ejected from expo with the option to use expoKit. We heard there are two ways to run the server in this state.

• to build in xcode after expo start
• to react-native run-ios orreact-native run-android in another tab after react-native start

If We run it the first time, it will work as before, but it doesn't load the native library properly. So We ran it the second way, and We get the following error. We think Bundler doesn't map it properly.

Here is a log of react-native start orreact-native start —reset-cache:

Some introduction:

Our app uses Heroku as a server. So, after pushing code it runs npm start as in my package.json

My current version of nodeJS in a laptop: v8.16.2, npm: 6.4.1.

In package.json:

"engines": { "node": "10.16.3", "npm": "6.9.0" },

The problem:

Currently, it runs like this "start": "node build/index.js" . Last changes were about adding graphql files.

npm start show Error: ENOENT: no such file or directory, open '/app/build/apollo/nCourse/nCourse.graphql'

We don't run with node server/index.js because of using new ecma script features(not common js) like import and export

The question

I see two solutions in this problem

1. Make something which will create the file with graphql extension in build folder

2. Maybe update version of nodeJS if it can understand es import and export

Package.json