Changelog

This release fixes some bugs that will improve jxscout's completeness:

• Fixed a bug where jxscout was not downloading webpack chunks that required authentication
• Fixed a bug where jxscout was not downloading source maps that required authentication
• Fixed a bug where jxscout was not downloading application/ld+json inline scripts

This release introduces the MCP server and miscellaneous performance improvements.

MCP Server

The era of hackbots is here and jxscout is ready to help you build them. This version introduces a MCP server with 3 tools that can help you build hackbots:

• get_html_routes - Allows the agent to get all HTML pages tracked by jxscout for the current project.
• get_js_files_loaded_by_html_file - Allows the agent to list all loaded JavaScript files for a given route. This includes discovered Webpack chunks, reversed sourcemaps and optimized versions of the JavaScript files.
• get_static_analysis_results_for_file_paths - Allows the agent to get static analysis results from jxscout. This allows the agent to get discovered paths, and other relevant parts of the code, so it can focus on what's important.

By default the MCP server will be running on port 3334 under the /mcp route. You can use the config command on the CLI to change the port. Here is an example configuration for Cursor:{ "mcpServers": { "jxscout": { "url": "http://localhost:3334/mcp" } } }

This is the first version of the MCP server. I'm excited to get feedback on other tools that you would like to see.

Miscellaneous Improvements

• The query to get project level descriptors was improved and should now be faster
• Descriptors are now sorted alphabetically by default

This release includes some quality of life improvements to the VSCode extension.

• Deprecated the toggle sort button since results are sorted by the backend automatically
• You can now quickly navigate to specific routes of the current project by bringing up the VSCode command palette (Ctrl+Shift+P) and selecting "jxscout: Go to Route".
• Project level views are now cached in memory, so you can switch between File and Project scope without waiting for the results to be loaded from the backend.

This is a big release that introduces numerous important bug fixes and improvements to asset navigation in VSCode. Even though there should be no breaking changes, I recommend creating a backup of your existing projects as there were some changes in the way sourcemaps are saved.

To backup your projects, you can use the following commands:

$ cp -R ~/jxscout ~/jxscoutbak$ cp -R ~/.jxscout ~/.jxscoutbak

⚠️ This release was only tested on macOS yet. If you are on a different OS, please let me know if you encounter any issues.

Webpack Chunk Discovery

• Fixed a bug where websites that returned a 200 with HTML content for brute-forced webpack chunks caused jxscout to download those "No Content" HTML pages

Reversed Sourcemaps

• Improved the way reversed sourcemaps are saved to disk. Previously all reversed sourcemaps were saved underneath the hostname path, but this could cause conflicts between different parts of the application with available sourcemaps.
• Sourcemaps are now saved in a directory relative to where they were found (e.g., https://example.com/assets/js/app.js.map will be saved to example.com/assets/js/src/...)
• This change mimics the way sourcemaps are reversed and shown in the "Sources" tab of Chrome.

Improved Asset Relationship Tracking

• Scripts loaded with the crossorigin attribute were not being related to the loading route. This is because jxscout relied on the Referer header to determine the loading route, but with that attribute set, the Referer header is not sent.
• jxscout now keeps track of scripts loaded by HTML pages and attempts to relate them to the loading route.

Improved Asset Navigation

• Implemented the backend changes to support the new asset navigation updates in VSCode.
• See the VSCode 1.1.0 changelog for more details.

This release includes numerous improvements to the UX for navigating assets in the VSCode extension. Please update the CLI version to 1.1.0 as well to get the latest features.

Added ability to hide descriptors

jxscout has many descriptors, and some of them might not be relevant to you. You can now hide descriptor types by right-clicking on them.

Improved asset navigation

The assets view now shows the assets in a tree structure, making it easier to navigate.

Ability to "lock" views

When changing between files, the descriptors and assets views update their results by default. You can now lock those views to prevent updating them when jumping between files.

This feature should be useful if you are analyzing a particular route. You can select the HTML file you want to analyze, which will make jxscout load all the assets/descriptors for that route. Then you can lock the views and analyze all the relevant code for that particular route.

Improved asset search

The previous version's search view was not very useful. Now search is done in memory and updates in real time, which should result in a better experience.

You can also search for assets within the "Assets" view by bringing up the VSCode command palette (Ctrl+Shift+P) and selecting "jxscout: Go to Asset", which opens a quick pick view to search for assets.

This is the first release of jxscout pro with a proper changelog. Going forward, every release will include detailed changelog entries to better communicate changes to users.

This release also introduces a new versioning scheme. Previously, releases were versioned using dates, but this approach doesn't work well for versioning. I've now adopted semantic versioning for better compatibility and clarity.

Versioning: Semantic Versioning

Adopted semantic versioning (major.minor.patch) with the following rules:

• Major: Incremented when breaking changes are made to the communication protocol with the VSCode extension
• Minor: Incremented when new features are added
• Patch: Incremented when bugs or small improvements are made

New Feature: Multi-file Descriptor Selection

You can now select multiple files or directories in VSCode to get descriptors for them simultaneously. This provides a more efficient workflow when analyzing multiple files.

Improvements and bug fixes

• Deprecated the "Filter descriptors by file path" searchbox in favor of the new multi-file selection feature
• Added the ability to cancel in-flight requests when switching away from the project-level descriptors view
• Duplicate descriptors are now automatically collapsed into single entries for cleaner visualization

Implemented changes to support getting descriptors for selected files. See the CLI changelog for more details.