I update my react-admin version from 2.5.2 to 2.8.0 and all react-admin's native buttons (edit/create etc) and resources labels have changed.
There are some cases I was able to fix it, for example changing every EditButton to have label='edit' prop, but how can I change it in other components? like <Resource> or <List> or the create button rendered in <Create>? has anyone encountered this and knows to explain why this happened?
please see attached img for more details, the unexpected labels are marked with red.
*** EDIT ***
After further investigating this issue I came across this issue on their repo, many users had this issue when upgrading react-admin.
I can confirom this was fixed by removing package-lock.json, node_modules and running npm install.
Related
Recently upgraded React-Admin in our project from 3.16.2 to 3.18.1 and noticed a bunch of the UI strings changed.
Where it previously said, 'ADD FILTER' or 'CREATE' it now says, 'RA.ACTION.ADD_FILTER' and 'RA.ACTION.CREATE'
We weren't passing an i18nProvider prop to the <Admin> component.
After the strings changed, I thought maybe it was required now, but adding one seems to have no effect.
package.json looks like this
"react-admin": "^3.18.1",
"ra-language-english": "^3.18.0",
"ra-i18n-polyglot": "^3.18.0",
Did some googling and found one similar sounding issue, but with no solution.
Has anyone else run into anything like this? Thanks.
Great suggestion by Gildas to use yarn.
For those wondering, got up and running very quickly by running:
npm install -g yarn
yarn
yarn start
Some additional helpful info in the yarn docs.
I am getting this warning with using Swipeout:
"
Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See
Move data fetching code or side effects to componentDidUpdate.
If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: *** to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.
Please update the following components: Swipeout
"
Same thing for componentWillMount.
Of note, using npx react-codemod rename-unsafe-lifecycles does not work to alleviate this error.
I went into the code for Swipeout and manually added the UNSAFE_ but every time I compile the code, it reverts back.
I've opened up an issue with the page on GitHub but no response after several days.
Suggestions?
Thank you,
Meanwhile, I'd recommend you fork the project. Make the change, remove the OG package from your dependencies and install your own fork with:
npm install <YOUR-GITHUB-USERNAME>/<YOUR-REPO-NAME>
Oh, and while you're at it, if you've got the time, send them a pull request ;)
I keep receiving this error when running my App.js for React Native that was working perfectly well before I attempted installing Victory charts. Somehow something broke and after over three hours of work I am unable to figure out a solution. I have tried everything I could find on the web including uninstalling watchman, reinstalling watchman, reverting to React Native 0.55.4, some other recommended commands. Nothing is working.I am so confused.
$ yarn add react-native-scripts
This helped.
I think the other library may hurt the installation part of your package. To solve this issue on IOS you need to add its library like below:
First do 'yarn add react-native-scripts'. In the case that it dose't work continue other steps.
1-Go to the node module of your project and find the package folder and find the ios file inside it.
2- Then drag it into ‘library’ section of your xcode. (It is the subset of your project folders)
3- Then go to ‘build phase’ and in the ‘Link binary with libraries’ add it there by clicking on the plus sign
4- Then in some cases you need to add the correct path of the ios file inside your node module in the xcode. To do that you should go to ‘build setting’ section in the xcode and search header there. Then you need to add the path there below other paths.
5- Then clear everything (cmd+shift+k) and then finally compile it.
I hope it works for you.
In my case the "crna-entry.js" file does exist in the roots and my project should work (nothing have been modified from last time when it does work).
After hours searching, finally I figured out the reason:
the packager's directory checking is case-sensitive and in windows terminal the drive "c:/" will not be auto-corrected to "C:/" which will lead to error.
Hope this will help someone who gets the same error.
Below is the full error message:
The development server returned response error code:404 Cannot find
entry file node_modules/react-native-scripts/build/bin/crna-entry.js
in any of the roots:
I'm simply trying to import 'aurelia-event-aggregator' into a TypeScript class and I get this error in my console. Even though it says it's loaded and configured aurelia-event-aggregator on lines 5 & 6, it says SystemJS still can't find it. This is especially strange since I'm also (successfully) importing autoinject from 'aurelia-dependency-injection' and customElement from 'aurelia-framework' without a problem, and they seem to be configured/installed identically to the event aggregator on my system via jspm.
My config.js and package.json are here.
I haven't the slightest idea how to start troubleshooting this. Please let me know if there's any other information I can provide.
This is going to sound dumb, but you need to run jspm install aurelia-event-aggregator. I know it's already in your project, but jspm 0.16 doesn't support peer dependencies (at least that's what I remember), so you have to explicitly install it as a top level dep for your app and then it will start working.
I've performed an update from typo3 4.7.20 to 6.2.15. The process worked fine and there were no critical errors while running the install tool.
The frontend looks fine but the backend is broken:
I've removed all uncompatible extensions before I run the update. I've also checked all settings in the installationtool und deleted the temp/cache folder first.
I've got the feeling that the error is caused by the TemplaVoila! extension, I'm using v. 1.9.8. Firebug does not shows any error.
Does anyone had a similar problem and have already solved it?
Thank you very much!
I have come across this one multiple times. More often it is because there is a broken TBE_STYLES. I suggest you look around for $TBE_STYLES in your typo3conf folder and disable it for the time being. Most likely it will be in the extTables.php or some other file which is included dynamically.
seems BE is working, but you css does not got loaded.
check your 'web inspecter' to see if you get errors on loading CSS.
clear your cache (remove everything in typo3temp) and try again