Harsh Singh

I am having trouble reproducing this. If this has happened with anybody, please do let me know.

Hey @hrishioa, in the latest update of kmenu this will be fixed. I'm facing this bug too, but it happens only in development. It goes away in production,

It's been fixed in the recent `v1.0.0-beta-git` release. I'm unable to reproduce it, so I'll close it unless you still encounter it.

BTW, I'm aware I can escape the curly brackets by adding a forward slash infront, but the main issue I wanted to point out here was markdown files being processed...

Hey, @mhanuel26 which version of React are you using?

@mhanuel26 OH, you cloned this repository. I got confused and thought you faced this issue while running `yarn add kmenu`. The issue with this is in `@types/react`, and they have...

Clone the main repository, and just do `yarn` in the root directory. Then, you'll build the files using ` yarn build` and it'll automatically be built to the examples directory....

This was an issue with `@types/react` which required me to to edit the file, as I've told you to do before. > @mhanuel26 OH, you cloned this repository. I got...

Also, the build is failing, not the installation. Everything has installed properly, you just need to edit the type definitions for `@types/react` :smile:.

@mhanuel26 you do not need to install `kmenu` from NPM, I'm telling you this over and over again :smile: I'm assuming the reason your build process isn't working is because...