with new react-navigation v5 it's become impossible to use it with react-native-web.
just importing createBrowserApp throws an error
import {createBrowserApp} from "#react-navigation/web";
show following error in #react-navigation/web/dist/Link.js
TypeError: (0 , _core.withNavigation) is not a function
does anybody know how to use now react-navigation v5 with react-native-web? I need url history in path, but now it has became impossible.
expo install react-navigation react-native-gesture-handler react-native-reanimated react-native-screens
npm i react-navigation-stack
npm i #react-navigation/web
install with expo that is why expo would look for the correct version of the react–navigation libraries that’d work with the expo version that’s installed in your project.
and keep with this tutorial
https://codersera.com/blog/how-to-do-navigation-in-react-native-web-in-2020/
Related
I'm Create new Nuxt3 App with command npx nuxi init nuxt-app in my Mac mini m1
After cd to nuxt-app and run yarn install completed.
I Can't run command yarn dev
It's throw Error Unexpected token '||='
Any One found this Error like me ? what solution you did ?
My error was happened on Official Code Sandbox link from NUXT Official Website too.
Nuxt3 Official Codesandbox
I don't really understand how to edit the codeSandbox.
But after some research the sign ||= is a new operator understand by node.
So your version of node doesn't understand the operator, try to update to the latest (stable) version, it's expected to work after the version >=15.0.
I'm beginner in react-native and I doing steps in a website of react-native
and the app is working right,
but after doing some update
npm i react#latest --save
npm i react-native#latest --save
react-native upgrade
after that, I can't create any project by
react-native init projectName
I get this error
image link
This is actually a problem on Windows with the latest version of react native (0.56)
GitHub Issue
Try using version 0.55.4 by typing react-native init --version="0.55.4" projectName
Not every version of react-native is compatible with every version of react. In the screenshot you sent, it says you need react#16.4.1 for react-native#0.56.0. Try doing npm i react#16.4.1 --save and then try react-native init projectName again.
After an npm install which triggered meteor-client bundle during postinstall, I am receiving this new error in the browser console:
"ReferenceError: Meteor is not defined
at Object.eval (webpack-internal:///../../../../meteor-client.js:32502:3)
at eval (webpack-internal:///../../../../meteor-client.js:32507:30)
at Object.../../../../meteor-client.js (http://localhost:4200/vendor.bundle.js:1395:1)
at __webpack_require__ (http://localhost:4200/inline.bundle.js:55:30)
at eval (webpack-internal:///../../../../../clients/browser/main.ts:3:72)
at Object.../../../../../clients/browser/main.ts (http://localhost:4200/main.bundle.js:424:1)
at __webpack_require__ (http://localhost:4200/inline.bundle.js:55:30)
at Object.0 (http://localhost:4200/main.bundle.js:439:18)
at __webpack_require__ (http://localhost:4200/inline.bundle.js:55:30)
at webpackJsonpCallback (http://localhost:4200/inline.bundle.js:26:23)"
```
Triggered at:
if (Package.reload) {
Meteor._reload.onMigrate(function () {
return [false];
});
}
This behavior occurs with:
#angular/cli: both 1.6.3 & 1.6.6
meteor-client-bundler: 0.3.0
Meteor: both 1.6.0.1 & 1.6.1
I had the same issue, and downgrade as John mentioned worked for me.
If you are wondering how to downgrade your meteor app follow the instructions bellow that I've taken from how do I install a previous version of meteor JS?
1) Go to your project root folder
2) Run meteor update --release x.y.z
Where x.y.z is the desired version, for example 1.6.0
Might be related to this issue with a normal angular-meteor setup? It seems like the Meteor version 1.6.0.1 is crashing the meteor-angular setup. I was testing both project setups, with and without AngularCLI, and experienced exactly the errors described here and at angular-meteor issues.
However, resetting the project to Meteor 1.6 worked for me in both cases.
I'm trying to get a fresh react fine uploader going but keep running into issues with react-addons-css-transition-group.
The warning I'm getting is:
npm WARN react-fine-uploader#1.0.1 requires a peer of
react-addons-css-transition-group#0.14.x || 15.x.x but none was
installed.
I've installed the latest version of React i.e. 15.5.4 and according to this page, the react-addons-css-transition-group has been deprecated.
https://www.npmjs.com/package/react-addons-css-transition-group
How do I resolve this issue?
P.S. This is my package.json file as it stands right now.
I just updated to React Native 0.21, but I am getting an error when I require Parse:
var Parse = require('parse/react-native').Parse;
The error I get is:
undefined is not a constructor (evaluating 'new _weakMap2.default()')
I don't believe it has to do with Parse though, as searching the directory, the 'weakMap2' reference is only found inside the react-proxy package.
Has anyone else experienced this error or found a workaround? Thanks!
This should be fixed in react-proxy#1.1.7.
(Don’t use 2.x, it’s not related to React Native at all currently!)
You can run npm install react-proxy#1.1.7 so NPM updates it locally. If you are using npm#2.x, you would need to run npm install react-proxy#1.1.7 inside node_modules/react-native/node_modules/react-transform-hmr or something like this—check where it is installed and make sure it’s 1.x but up to date.
Don't really know the issue but running Parse JS SDK as version 1.6.14 works for me. Have the same error as you when running latest 1.7.1. Hard to trace the error.
npm i parse#1.6.14 --save
I forced react-proxy to version 2.0.1 and the error is now gone for me.