We Keep Coding

Expo app thowing file missing error though files are actually present there

I am using pnpm to create expo app. Just created pnpm create expo-app, installed dependencies and then run yarn android === expo start --android.
Tried shamefully-hoisting as well as moving project to location with no spaces in path but each time I get the same error.
I manually checked, all the files that are shown missing in error are actually present there.
How do I fix this?
Error: Unable to resolve module ./node_modules\expo\AppEntry from C:\Users\HariC\AndroidStudioProjects\chat/.:
None of these files exist:
* node_modules\expo\AppEntry(.native|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx|.android.js|.native.js|.js|.android.jsx|.native.jsx|.jsx|.android.json|.native.json|.json)
* node_modules\expo\AppEntry\index(.native|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx|.android.js|.native.js|.js|.android.jsx|.native.jsx|.jsx|.android.json|.native.json|.json)
at ModuleResolver.resolveDependency (C:\Users\HariC\AndroidStudioProjects\chat\node_modules\.pnpm\metro#0.72.3\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:152:15)
at DependencyGraph.resolveDependency (C:\Users\HariC\AndroidStudioProjects\chat\node_modules\.pnpm\metro#0.72.3\node_modules\metro\src\node-haste\DependencyGraph.js:264:43)
at C:\Users\HariC\AndroidStudioProjects\chat\node_modules\.pnpm\metro#0.72.3\node_modules\metro\src\lib\transformHelpers.js:170:21
at Server._resolveRelativePath (C:\Users\HariC\AndroidStudioProjects\chat\node_modules\.pnpm\metro#0.72.3\node_modules\metro\src\Server.js:1196:12)
at async Server.requestProcessor [as _processBundleRequest] (C:\Users\HariC\AndroidStudioProjects\chat\node_modules\.pnpm\metro#0.72.3\node_modules\metro\src\Server.js:484:37)
at async Server._processRequest (C:\Users\HariC\AndroidStudioProjects\chat\node_modules\.pnpm\metro#0.72.3\node_modules\metro\src\Server.js:435:9)

Since android didn't work. I tried running web and I was prompted to install #expo/webpack-config. I installed it using expo install #expo/webpack-config#^0.17.2 and wow… It worked!

Error Failed to install the app. Make sure you have the Android development environment set up :React-Native

I created new project with react-native but isn't working because my react-native can't running even though emulator is open .I looked stackOverflow for solutions then I try to fix the error but react native still can't running.
This is error:
error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
FAILURE: Build failed with an exception.
What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.
SDK location not found. Define a valid SDK location with an ANDROID_HOME environment variable or by setting the sdk.dir path in your project's local properties file at 'D:\ReactNative\Boniki\android\local.properties'.

Electron fails to install on CI

After we migrated to Electron v11 for our project from v6, we started experiencing weird CI issues, where Electron did not install properly and the pipeline failed.
Our setup:
Lerna
Monorepo
Yarn v1.22
Private npm registry
Example of such issues:
[4/4] Building fresh packages...
error /builds/xxxx/..../node_modules/electron, /builds/.../node_modules/electron, /builds/xxxx/app/node_modules/electron: Command failed.
Exit code: 1
Command: node install.js
Arguments:
Directory: /builds/xxxx/features/yyyy/node_modules/electron
Output:
Error: dest already exists.
at /builds/xxxx/node_modules/fs-extra/lib/move/move.js:41:31
Exit code: 1
Command: node install.js
Arguments:
Directory: C:\gitlab\builds\pFMTxHs3\0\xxxxxx\features\yyyyy\node_modules\electron
Output:
C:\gitlab\builds\pFMTxHs3\0\xxxx\features\yyyyy\node_modules\electron\install.js:51
throw err
^
[Error: ENOENT: no such file or directory, open 'C:\Users\xxxx\AppData\Local\electron\Cache\httpsgithub.comelectronelectronreleasesdownloadv7.1.4electron-v7.1.4-win32-x64.zip\electron-v7.1.4-win32-x64.zip'] {
errno: -4058,
code: 'ENOENT',
syscall: 'open',
path: 'C:\\Users\\xxxx\\AppData\\Local\\electron\\Cache\\httpsgithub.comelectronelectronreleasesdownloadv7.1.4electron-v7.1.4-win32-x64.zip\\electron-v7.1.4-win32-x64.zip'
We tried deleting CI caches, Yarn caches, NPM caches all of that worked inconsistently. Sometimes we would have successful pipelines, sometimes not.

After a couple of months battling with this ghost, we had another error 5xx upon trying to download electron. It suddenly stopped downloading everywhere local machines and CI.
After getting in touch with the Electron team I discovered the problem.
We had a very old .npmrc config, which was no longer valid.
It contained this:
disturl=https://atom.io/download/electron
When I've changed the line into this:
disturl=https://electronjs.org/headers
All of our pain was gone - our builds became stable again.
Big thanks to the electron community!

Can't run a meteor project (Ubuntu 16.04)

I am using Ubuntu 16.04 and I have installed node.js, npm, nodejs-legacy (via terminal) and I launched the meteor installer from the offical meteor webpage.
Now I have following problem when I try to start my meteor project:
/home/fabian/.meteor/packages/meteor-tool/.1.4.1_2.354htk++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/meteor-promise/promise_server.js:165
throw error;
^
Error: ENOENT: no such file or directory, open
'/tmp/mt-1jeehae/os.json'
at Error (native)
I always get this error message - not only when I try to start my existing project - also when I try to create a new project - always the same message.
Does anybody know how to fix this problem? Thank you very much.

Meteor: Error: ENOTEMPTY: directory not empty when deploying to Modulus

I'm deploying a Meteor app to Modulus.io. I had no problems at all deploying it with modulus deploy in the last couple of days but after a couple of changes to my app I now get the following error:
Error: ENOTEMPTY: directory not empty
It happens at a very late stage of their script, here's the full log from the terminal:
deploy -> v0.10.36
Uploading completed build.
Provisioning and deploying bundle to servos...
fs.js:807
return binding.rmdir(pathModule._makeLong(path));
^
Error: ENOTEMPTY: directory not empty, rmdir '/Users/andreaswest/Documents/workspace/test2/.demeteorized'
at Error (native)
at Object.fs.rmdirSync (fs.js:807:18)
at Object.removeSync (/usr/local/lib/node_modules/modulus/node_modules/fs-tools/lib/fs-tools.js:420:8)
at /usr/local/lib/node_modules/modulus/lib/controllers/project.js:279:21
at /usr/local/lib/node_modules/modulus/lib/controllers/project.js:383:19
at /usr/local/lib/node_modules/modulus/lib/controllers/project.js:354:9
at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/modulus/lib/librarian/http.js:134:9)
at emitNone (events.js:73:20)
at IncomingMessage.emit (events.js:167:7)
at endReadableNT (_stream_readable.js:906:12)
Can anyone help?

This is the answer I got from David Berger from Modulus support:
Hey Andreas,
Sometimes this will happen and the deploy will have been successful, but the CLI failed to do a little cleanup afterwards. If your deploy is not working from the CLI, we recommend trying to deploy from the web dashboard: https://my.modulus.io/project/57316
If you deploy from the web dashboard, create a zip of your project files, and then upload it via the ‘deploy files’ upload in the upper right hand corner of the dashboard.