I'm looking at using Semantic UI in my meteor projects. When I try to run: meteor add semantic:ui I get an error from the terminal saying that the package doesn't exists, yet according the Semantic UI GitHub page it should?
semantic:ui is now Depcrecated , like they point on the nooitaf:semantic-ui package Atmosphere README
try with
meteor add semantic:ui-css
Using Deprecated (not a good choose)
meteor add nooitaf:semantic-ui
We're currently working on relaunching the package. We didnt correctly build the LESS theming into meteor's pipeline in the original package so it did not add any particular value over using semantic:ui-css.
The new package should launch in the next couple days and support theming.
Edit: We just launched the new package, won't be going away again :)
https://atmospherejs.com/semantic/ui
Related
TL;DR
Similar questions have been asked before on SO (such as Convert Expo project to Original React Native project, Commands to use after converting from expo to react-native-cli, and Expo to react native init) but none of them explain how to completely remove all Expo modules and dependencies from my project, so that I end up with a pure React Native app (the same as if I had run react-native init... in the first place).
So is it possible to remove all of this extra crap that I never asked for or expected to be installed, with one simple command? MTIA! :-)
Background
Basically I got into this mess by ejecting from a managed Expo project, then customising the android folder a lot before realising that my build/install times were ludicrously slow.
So to fix this, I ran yarn global add depcheck and depcheck, which suggested that I could/should remove all of the following packages (the most seemingly-important ones are marked with an asterisk):
expo-updates*
filtrex
firebase-admin
lodash
mathjs
moment
native-base
nodemailer
react-native-android-location-enabler
react-native-credit-card-input
react-native-document-picker
react-native-fast-image
react-native-geolocation-service
react-native-image-crop-picker
react-native-js-bottom-sheet
react-native-reanimated
react-native-signature-capture
react-native-unimodules*
react-native-web
react-timer-mixin
recyclerlistview
shortid
stripe-client
styled-system
#babel/core
#react-native-community/eslint-config
babel-jest
jest
prettier
react-test-renderer
So I blindly ran yarn remove ... on all of those packages, and now I get a ton of errors on attempting to build. I won't list them here since it's obvious that they're mostly (if not entirely) related to the expo-updates and react-native-unimodules packages marked above.
I'm not explicitly using anything Expo-related in my code, so this should be a cake walk IMO, but is proving to be quite difficult!
So how can I remove this extra cruft properly? Do I need to start fresh with react-native init? MTIA :-)
Ejected expo projects needs unimodules to function properly.so i don't think there is a simple command that does everything you asked for. You can follow some steps to get it working.
Branch out for safety.
Eject, check if it is working and commit.
Delete all except .git folder in the project(also can keep a copy of .git somewhere else if project is not stored remotely).
Do initiate a bare react-native project to the same folder(have to do it from parent folder with same project name as the current project folder name, it will prompt the folder is not empty. choose to continue).
Discard the deletion of the files with your Codes.
Add packages that use in project(for expo packages, find replacement packages. Most probably will be mentioned in expo documentation).
Run Project, (might get some missing dependencies.if so, add and rerun)
I have finally acheived this almost 6 hours later by:
Creating a new React Native app from scratch (react-native init MyAppName).
Finding replacements for all the Expo modules that were being used (not by me directly, but by other packages).
Reconfiguring my Firebase project to play nice with the app (particularly the SHA keys).
Uninstalling the old app, installing the new and clearing caches for the "new" app (I say "new" because I didn't expect this step to be necessary, but somehow, for some stupid reason, Android was trying to use the old, cached app files).
The last step was absolutely crucial; it took me about 2 hours of head scratching and screaming at the PC before I finally stumbled upon this: React Native white blank screen issue. Many thanks to #DiwakarPrasad for this absolute gem of knowledge!
I'm having trouble understanding what I have to do. I work on a Mac and I'm trying to create a 3d portfolio but for some reason, this is difficult. I am trying to figure out why JavaScript is not showing up on Variants. When I type "npm init vite.js/app" this gives me a Framework and then I choose Vanilla and then Select a variant should show up with JavaScript giving me a Package JSON.
Please help.
Vite changed how they display variants.
Just select vanilla if you want to use JavaScript. (not vanilla-ts, as that is the TypeScript version)
Vanilla means "without any modification, so in this case, the first "vanilla" means no library added (react, vue, svelte, etc.), and the second section means without TypeScript.
Remember to cd into that new app's directory and run npm install to install your packages.
I had a fully functioning react native app, and I tried to install the Facebook Login button. I followed these instructions:
https://developers.facebook.com/docs/react-native/login
and
https://developers.facebook.com/docs/react-native/configure-ios
There is a known issue using react-native link to connect the Facebook SDK to the project, and so I tried linking it manually. I could not get the Facebook Login to work, and now when I use react-native run-ios, my app just shows a black screen!
As a test, I used create-react-native-app to create a new app, and I launched it, and I'm getting this error:
this._lazyCallableModules[name] is not a function (MessageQueue.js 155:11)
Since I'm not sure what MessageQueue is and this is a brand new app, I'm not sure how to undo the damage I've done.
Has anyone experienced this, or do you at least have some idea of how I can go about resetting my react setup?
If I haven't given enough relevant information, please let me know.
Followed the answer given here and it's working well so far.
Downgrade the babel-preset-react-native package from 2.0.1 to 2.0.0. The command is npm install babel-preset-react-native#2.0.0. Use the --save flag if you want to store it to your package.json.
Updating to the latest React Native, clean & build solved it for me.
Sorry if this is a dumb question, I've tried to google for the answer and can't find anything definitive.
I added the following package https://atmospherejs.com/rcy/nouislider
by entering the command meteor add rcy:nouislider
I am unsure if there any more steps from here. Do I need to import the package at the top of my JS file or can I go ahead and just start using it without any other steps?
Atmosphere packages should not need to be imported. The older packaging system did that for you, and the global variable 'noUiSlider' should be available to your code for you to use like in the documentation.
If you are interested, you can download the package code and see how it's put together. Just like a Meteor project there is client and server code. See here for more details: https://guide.meteor.com/writing-atmosphere-packages.html
When I run both meteor add for both meteoric:ionic-sass and meteoric:ionicons.-sass, it shows the error below.
=> Errors while adding packages:
While checking for stevezhu:sass#1.3.7:
error: No compatible binary build found for this package. Contact the
package author and ask them to publish it for your platform.
I use a windows machine by the way..is that the problem? I have also posted on the Github page but I think it is not maintained or something.
I was having this issue with a different package while trying to work on a Windows machine. I ended up calling meteor update while in the directory for the meteor project I was working on and that fixed it.