-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing problem #16
Comments
Hey, @mhanuel26 which version of React are you using? |
Hi @harshhhdev , thanks for your quick response, In fact I think I handle to install it but I am not 100% sure if I did the correct way or if I even remember what I did lol, I cloned this repo, then I did yarn add kmenu on the example folder, then yarn install followed by yarn start. After that i was getting some issue related to ssl (sorry I don't have the log output anymore) which I fix by doing:
Now, I am wondering, if I have a working react base project, should I go and merge the package.json of examples with my existing file and do the same sequence to get this working ? Can you help me pointing me in the right direction please. Thanks in advance, |
@mhanuel26 OH, you cloned this repository. I got confused and thought you faced this issue while running The issue with this is in interface FunctionComponent<P = {}> {
(props: P, context?: any): ReactElement<any, any> | null;
propTypes?: WeakValidationMap<P> | undefined;
contextTypes?: ValidationMap<any> | undefined;
defaultProps?: Partial<P> | undefined;
displayName?: string | undefined;
} With: interface FunctionComponent<P = {}> {
(props: PropsWithChildren<P>, context?: any): ReactElement<any, any> | null;
propTypes?: WeakValidationMap<P> | undefined;
contextTypes?: ValidationMap<any> | undefined;
defaultProps?: Partial<P> | undefined;
displayName?: string | undefined;
} This should solve the issue! Please let me know if it does. |
Hi @harshhhdev , Sorry, I did not follow you entirely, I understand now that if I run I want to understand this process in order to add kmenu to my skeleton project. Now regarding the issue I am actually seeing, please look at the following I think the workaround you suggest is not for this but I did anyway Could you please enlight me? Thanks in advance, |
Clone the main repository, and just do |
Hi @harshhhdev , I start over and after doing
What am I missing then? Thanks, |
This was an issue with
|
Also, the build is failing, not the installation. Everything has installed properly, you just need to edit the type definitions for |
Hello @harshhhdev , The build process does not work for me, the only way I have managed to run the example on my ubuntu 22.04 is: cd into the example directory and install there
|
@mhanuel26 you do not need to install I'm assuming the reason your build process isn't working is because you haven't setup the types properly, and I've already told you how to do that above. If there's a different issue, please let me know and be descriptive with your error messages. |
@harshhhdev , When you first clone the repository, the @types/react does not exist, then I do yarn on root folder, this create the node folder, are we ok to this step? This step will end up in failure.
Now, after this I can modify the @types/react as you mentioned, then I do yarn build, it fails too. At this point I do again yarn again, selecting the same installer, error again, if I do select different installer (0.13.11 on image above), my @types/react file get overwritten. Can you realize that I am modifying the file and execute the commands you point me but still getting the error? Please give me your comments? |
Hey @mhanuel26, I'm not sure why it's giving you those errors. The build works just fine for me with |
I am getting an error while running add kmenu using yarn
I do have node 18 .
Can you advice please?
The text was updated successfully, but these errors were encountered: