Lukasz Gornicki

I did ``` npm run clean npm install npm run start ``` on node 20 on master and playground renders well when I switch to your branch, installation fails witj...

@ductaily after your recent update, installation works, and playground renders as expected - not sure what should I do to replicate your issue

@kennethaasan you're completely right. Tbh I though that for playground we did it already as anyway playground is not released to npm. Btw, @char0n that wrote the article that you...

sorry for being late, we had some issues. Me and few other maintainers lost funding https://www.asyncapi.com/blog/2024-june-summary#postman-partnership-changes. Please join AsyncAPI Slack where you can ping me when you see an unusual...

Please try with latest `1.4.2` and also older node version. We do not test against node 20 yet and our internal playground builds well against node 18

🤔 `fs` comes from parser that has a read file functionality, but we had proper webpack in place to make sure package still works in browser 🤔 https://github.com/asyncapi/asyncapi-react/blob/master/library/webpack.config.js#L50

we need more support here in this project and prefer PRs with fixes. @magicmatatjahu wouldn't be the best from developer experience if we make sure `parser-js` also publish separately package...

I'm using docpad 6.63.3 and also have the same issue, partial in pre/code fails with exactly the same issue. @MohammadYounes did you solved it somehow?

ok, so for now as a workaround I'm using `` to disable highlight plugin to process my code snippet so no errors. Hope some smart guy can look at it...

didn't you forget about setting target? git remote add target https://github.com/username/username.github.io.git