Repo Outdated: Build Fails Due to Invalid Dependency, Parser API Changes & Node Compatibility Issues
Hi team,
I tried setting up EDAVisualiser locally to contribute, but ran into a few issues that make the repo impossible to install or build right now. Looks like it's mainly due to outdated dependencies and breaking changes in the AsyncAPI ecosystem.
1. Example React app uses a non-existent package version
Inside examples/simple-react/package.json:
"@asyncapi/edavisualiser": "0.15.1"
But the npm registry shows only version 1.2.0.
Since 0.15.1 doesn't exist, installation fails with:
npm ERR! 404 Not Found: edavisualiser-0.15.1.tgz
2. Library build fails because of parser v3 API changes
The code imports:
import { AsyncAPIDocument } from "@asyncapi/parser";
But parser v3+ removed AsyncAPIDocument, Channel, Server, etc.
This causes many TypeScript errors like:
TS2724: no exported member 'AsyncAPIDocument'
TS18046: 'channel' is of type 'unknown'
Pinning the parser to:
@asyncapi/[email protected]
makes it compile again.
Summary
- Example app can't install
- Library can't build
- Parser API mismatch
- Repo doesn’t seem updated for 2–3 years
Suggested fixes (happy to open a PR after approval)
- Update example app to a valid version or local path
- Pin parser to v1.16.0
- Fix TypeScript errors
- Possibly update the monorepo tooling
Question
Is EDAVisualiser still actively maintained, or has it been deprecated/replaced?
I’d be happy to help fix these issues — just want to confirm the project status before opening a PR.
Thanks! 😊
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
Hey @RanaPoddar are you willing to work on this? if not I'd like to work in this, thanks :)
Yes, @shubham220420 I’m working on this 🙂
I’m currently preparing a PR to fix the dependency + parser issues.
I opened the issue mainly to confirm whether EDAVisualiser is still active and if these fixes are aligned with the maintainers’ plans.
I’ll keep you posted, thanks!