Skip to content

Conversation

Ruchip16
Copy link

@Ruchip16 Ruchip16 commented Oct 16, 2025

Description

  • This PR is for the blog publishing for the latest web compatibility feature that we merged and released in v1.0.0 of vs-asyncapi-preview extension

Related issue(s)

Fixes #4450

Summary by CodeRabbit

  • Documentation
    • Published blog post announcing AsyncAPI VS Code Preview extension is now available in web browsers
    • Provides instructions for accessing and using the preview functionality via vscode.dev and github.dev environments
    • Documents technical updates and future possibilities for the extension

Copy link

netlify bot commented Oct 16, 2025

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit fa010e1
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/68f0c4575805170008d2c9ed
😎 Deploy Preview https://deploy-preview-4484--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@asyncapi-bot
Copy link
Contributor

asyncapi-bot commented Oct 16, 2025

We require all PRs to follow Conventional Commits specification.
More details 👇🏼

 No release type found in pull request title "AsyncAPI VS Code Preview Goes Web: Now Available in Your Browser 🚀". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide 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.

Copy link
Contributor

coderabbitai bot commented Oct 16, 2025

Walkthrough

Two files are added: a TypeScript declaration file for Next.js type references and a new blog post announcing web browser compatibility for the AsyncAPI VS Code Preview extension.

Changes

Cohort / File(s) Summary
TypeScript Configuration
next-env.d.ts
New TypeScript declaration file with reference directives for Next.js types and local routes, includes standard Next.js documentation note
Blog Content
pages/blog/asyncapi-vs-code-preview-goes-web-now-available-in-your-browser-.md
New blog post announcing AsyncAPI VS Code Preview extension web compatibility, covering technical changes (removal of Node.js-specific modules, browser utilities, updated dependencies), usage instructions, maintenance mode status, and community call-to-action

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

The TypeScript declaration file is trivial boilerplate. The blog post requires straightforward content review for clarity and accuracy, with no code logic to evaluate.

Possibly related PRs

Suggested labels

ready-to-merge

Suggested reviewers

  • derberg
  • thulieblack
  • akshatnema
  • anshgoyalevil
  • sambhavgupta0705
  • Mayaleeeee

Poem

🐰 A web extension hops into the browser with glee,
No Node.js chains, now running wild and free,
TypeScript declarations guide the way so bright,
AsyncAPI preview shines in vscode.dev's light! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Out of Scope Changes Check ⚠️ Warning The pull request introduces a next-env.d.ts TypeScript declaration file that is unrelated to the blog post requirements defined in issue #4450 and does not contribute to the content or functionality of the blog post. This addition falls outside the scope of the linked issue, which focuses solely on publishing the article. Please remove the next-env.d.ts file from this pull request and commit it separately if needed, so that only blog-related changes are included under issue #4450.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title succinctly and accurately conveys the primary change by announcing that the AsyncAPI VS Code Preview extension now works in the browser, directly aligning with the content added in the blog post. It is clear and specific, making it easily understandable to colleagues reviewing the pull request.
Linked Issues Check ✅ Passed The pull request adds a complete blog post that adheres to the structure and requirements of issue #4450 by including appropriate front matter, a descriptive title, an overview of changes under the hood, usage instructions, maintenance details, and a closing section. The content clearly explains the web compatibility feature and guides users on how to try it out, fulfilling the linked issue’s objectives for blog publication.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

codecov bot commented Oct 16, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (9de49c1) to head (fa010e1).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #4484   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          778       778           
  Branches       144       144           
=========================================
  Hits           778       778           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@asyncapi-bot
Copy link
Contributor

asyncapi-bot commented Oct 16, 2025

⚡️ Lighthouse report for the changes in this PR:

Category Score
🔴 Performance 38
🟢 Accessibility 98
🟢 Best practices 92
🟢 SEO 100
🔴 PWA 33

Lighthouse ran on https://deploy-preview-4484--asyncapi-website.netlify.app/

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9de49c1 and fa010e1.

📒 Files selected for processing (2)
  • next-env.d.ts (1 hunks)
  • pages/blog/asyncapi-vs-code-preview-goes-web-now-available-in-your-browser-.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
pages/blog/asyncapi-vs-code-preview-goes-web-now-available-in-your-browser-.md

[uncategorized] ~20-~20: The official name of this software platform is spelled with a capital “H”.
Context: ...Open any GitHub repo in vscode.dev or github.dev, and you can instantly preview As...

(GITHUB)


[grammar] ~21-~21: There might be a mistake here.
Context: ...your browser and an internet connection. 🔄 **Works consistently across desktop a...

(QB_NEW_EN)


[grammar] ~22-~22: There might be a mistake here.
Context: ..., providing the same preview experience. ## What Changed Under the Hood? Making the...

(QB_NEW_EN)


[style] ~30-~30: Consider using “incompatible” to avoid wordiness.
Context: ...Removed EDAVisualizer* (unmaintained, not compatible with webmode) - **Updated VS Code depen...

(NOT_ABLE_PREMIUM)


[grammar] ~37-~37: There might be a mistake here.
Context: ...lone repos locally just to preview files 🚀 **Teams adopting AsyncAPI in cloud-fi...

(QB_NEW_EN)


[grammar] ~38-~38: There might be a mistake here.
Context: ...rkflows** - Work entirely in the browser 💡 New users experimenting without n...

(QB_NEW_EN)


[grammar] ~39-~39: There might be a mistake here.
Context: ...ing** without needing to install VS Code This is a huge usability improvement...

(QB_NEW_EN)


[grammar] ~48-~48: There might be a mistake here.
Context: ...ll render beautifully in your browser 🚀 ## See It in Action *[Video demo section -...

(QB_NEW_EN)


[style] ~74-~74: For conciseness, consider replacing this expression with an adverb.
Context: ...ity - No new major features are planned at the moment - Community contributions for bug fixes...

(AT_THE_MOMENT)

@@ -0,0 +1,85 @@
---
title: AsyncAPI VS Code Preview Goes Web: Now Available in Your Browser 🚀
date: 2025-10-14T3:45:29+05:30
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Fix ISO-8601 timestamp formatting

The hour in the date field needs two digits (e.g., T03 instead of T3). Without the leading zero, the timestamp is invalid ISO-8601 and risks breaking date parsing in the site build pipeline. Please pad the hour with a zero.

🤖 Prompt for AI Agents
In
pages/blog/asyncapi-vs-code-preview-goes-web-now-available-in-your-browser-.md
around line 3, the ISO-8601 timestamp in the date field uses a single-digit hour
("T3") which is invalid; update the timestamp to pad the hour to two digits
(e.g., change T3 to T03) so the date reads like 2025-10-14T03:45:29+05:30.

Comment on lines +52 to +58
*[Video demo section - placeholder for showcasing the web extension in action]*

<!-- TODO: Add video demo showing:
- Opening a GitHub repo in vscode.dev
- Installing the AsyncAPI Preview extension
- Previewing an AsyncAPI file in the browser
- Highlighting the seamless experience -->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Remove placeholder + TODO before publishing

The published article currently shows “[Video demo section - placeholder…]” alongside an inline TODO block. Ship-ready content shouldn’t expose placeholders/TODOs to readers. Please either add the actual video content now or remove the section entirely.

🤖 Prompt for AI Agents
In
pages/blog/asyncapi-vs-code-preview-goes-web-now-available-in-your-browser-.md
around lines 52 to 58, remove the placeholder line "*[Video demo section -
placeholder for showcasing the web extension in action]*" and the HTML TODO
block; if you have the demo video ready, replace that whole block with the
embedded video or a linked thumbnail and a short caption describing the steps
shown (opening a GitHub repo in vscode.dev, installing the AsyncAPI Preview
extension, previewing a file, highlighting the experience); otherwise delete the
section entirely so no placeholders or TODOs remain in the published article.


- **Removed Node.js-specific modules** like `fs`, `path`, and external dependencies that are incompatible with browsers
- **Introduced lightweight browser utilities** (`pathUtils`) for cross-platform file handling
- **Removed EDAVisualizer** (unmaintained, not compatible with webmode)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

replace with:

  • Removed EDAVisualizer integration (unmaintained, not compatible with webmode)

because the integration is what is unmaintained


## See It in Action

*[Video demo section - placeholder for showcasing the web extension in action]*
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you need to add this section before aproving

@AceTheCreator
Copy link
Member

We require all PRs to follow Conventional Commits specification. More details 👇🏼

 No release type found in pull request title "AsyncAPI VS Code Preview Goes Web: Now Available in Your Browser 🚀". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@Ruchip16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enable web compatibility for VS Code Preview Extension

4 participants