I am trying to create Electron package for OSX however I am ending up having the following error.
The strict-ssl parameter is deprecated, use download.strictSSL instead
Cannot create symlinks; skipping darwin platform
Please help. Many Thanks.
I am running the following command
electron-packager . --out=dist/osx --platform=darwin --arch=x64
This is a bug. Still not really fixed with 7.0.1.
https://github.com/electron-userland/electron-packager/issues/349
Related
I am working on an expo project and everything is working fine, but I began to get a warning message when android is building as
Warning: Invalid version react-native#0.64.2 for expo sdkVersion 43.0.0. Use react-native#0.64.3
The app is still running fine but I don't how to fix this error yet and I want to know if it won't cause an issue later.
I have tried to run npx react-native upgrade 0.64.3 but it didn't work, I got this error
info Fetching diff between v0.64.2 and v0.64.3... error Fetch request
failed with status 404: 404: Not Found. error Failed to fetch diff for
react-native#0.64.3. Maybe it's not released yet?
changing the version of react-native manually in the package.json and run expo install worked for me
I use the expo doctor command it allows diagnose issues with the project.
I would recommend using the expo upgrade command. It upgrades the project packages and config for the given SDK version.
More to find here.
I just faced the same issue. Basically it's telling you should use a higher version of your react-native. I solved it just by updating it to the specified version.
npx react-native upgrade 0.64.3
More info here.
Cheers,
If as in my case one need a specific version of react-native, let's say older because some legacy dependencies in a particular project that for some reason can't be upgrade, then change the version in the package.json won't work.
What worked as the cli suggested is to use:
expo doctor --fix-dependencies
That installed the correct lower version of react-native
To find out actual problems run this command :
expo doctor
To solve all problems regarding package conflicts run this command:
expo doctor --fix-dependencies
Use sudo on Unix based OS if you have permission issue to run those commands.
To solve the error, I used the below command:
npm install react-native-clean-project --save-dev
It is a library that allows us to resolve conflicts.
This library is added to your dependencies.
This handles the problem and if it is not the case add this command:
react-native clean-project-auto
I just created a brand new React Native project, and I can't get it to run. The server always fails on the following:
node_modules/react-native/node_modules/#react-native-community/cli/build/commands/doctor/healthchecks/index.js:48
} catch {}
^
SyntaxError: Unexpected token {
The only thing I've found on this issue is this thread, which ends with people saying to post this question on Stackoverflow, hence why I'm here. I've tried the usual: upgrading node versions, removing node_modules and reinstalling, restarting my machine, all to no avail. I even delved into the code to see if I could figure out what's going on, but nothing jumped out at me.
My hope is that others have run into this with new React Native projects and that someone can help me resolve it. Any suggestions are welcome. Thanks!
Sigh.... Well after struggling with this for a day I found the workaround was to run npx react-native start in one console and then run npx react-native run-ios in another. I was just trying to do the latter by itself (which always worked in the past), and I guess that doesn't work anymore.
Probably your node and/or npm version is to old. Check by npm -v and node -v and update to latest version, or suggesting by react-native crew in dependencies from node site. Or if you use nvm try:
nvm install 16.14.0 && nvm alias default 16.14.0 && nvm use 16.14.0
Note that, this is for specific version. For latest, type:
nvm install --lts --latest-npm
nvm use x.x.x //latest installed version
This problem is due to node version. Upgrade your node verion above 12. It will solve the problem.
Use can either use nvm or directly install the node
if you are using android studio start it with command line
like this cd /path/to/android-studio/bin
then studio.sh make sure its executable
I am using orocommerce 4.2.1 from AWS marketplace. I made some changes in scss and want to build the assets. When i run the command php74 bin/console oro:assets:build --env=prod
I get the following:
[centos#ip-172-31-28-85 commerce]$ php74 bin/console oro:assets:build --env=prod
Building assets.
'/usr/bin/node' './node_modules/webpack/bin/webpack.js' '--hide-modules' '--mode=production' '--env.stats=' '--env.symfony=prod' '--colors'
[webpack-cli] Error: Unknown option '--hide-modules'
[webpack-cli] Run 'webpack --help' to see available commands and options
In OroAssetsBuildCommand.php line 247:
How can I remove this --hide-modules. I tried removing from package.json but nothing works?
It seems you have upgraded the "webpack-cli" NPM package to 4, but the OroCommerce 4.2 LTS is compatible only with "^3.3.12". To fix an error, you have to downgrade the package back to 3.3.12 version.
It's works for me
You can remove --hide-modules.
However, it is recommended that you use the mix executable. Please refer to the upgrade guide: https://github.com/JeffreyWay/laravel-mix/blob/628f6062cceb77610b1813e3179abcbd043a4642/UPGRADE.md#update-your-npm-scripts
After NativeScript install like that: https://docs.nativescript.org/start/ns-setup-os-x
When I ran the tns doctor command, only to find that command not found.
How can I resolve this issue?
You can following the instructions here. Please be sure,
install Node.js here
execute npm install -g nativescript
If you have installed both Node.js and nativescript, and you are still unable to execute tns doctor, you might check if the installation path is part of your PATH environment variable.
Find where NativeScript installed to on your computer Point your
various bash profiles there. For your reference,
I used this: PATH=$PATH:/usr/local/bin/lib/node_modules/nativescript/bin
Just curious, but have you tried source ~/.bash_profile?
I am struggling to understand why trying to run a npm install fails when one of the packages in the list is deprecated. A warning shouldn't make the command fail, shouldn't it?
I found the culprit PR. They created a version that hard breaks..
https://github.com/aspnet/SignalR/pull/2057
Got to love MS..