Since website needs javascript to render, any way to fetch the changes to give context to AI?

[johhansantana]

Question

I'm wondering if there is some kind API that one could fetch the changes to be able to give context to an LLM.

Right now if you point it directly to the website since it's a SPA it requires javascript so the LLM will not be able to see the content.

[tallen11]

Seconding this, today I very painlessly used Claude Code to upgrade an old RN project by simply giving it the patch notes from the upgrade-helper. All I did was copy the text on the page into a file and told Claude Code to use it and it worked. It would be great to have some kind of raw text output of the whole page that is easily ingestible by LLMs to make this process even smoother.

[johhansantana]

hey just wanted to write what i did as a workaround

I went into the rn-diff-purge repository where I believe this SPA gets its information and went into their diff chart here:

https://react-native-community.github.io/rn-diff-purge/

Then choose the correct versions and copied the url. You can then download the .diff file via curl (prompt your AI to download the .diff file via curl) and then add that file as context when you want to update the files for the update.

This has worked pretty consistently for me so far with sonnet 4.

[wong2]

@johhansantana That works great! So a simple solution is to add a link to the diff in the upgrade tool.

[htutwaiphyoe]

Yes, we need this for AI agaent capability.

[kelset]

Hey folks — I'm doing a maintenance pass on the repo and catching up on older issues/PRs.

I just closed #415 as a duplicate of this one so the conversation about AI-friendly access / export can stay consolidated here.

There is also an open PR in this area now: #419. It looks like a useful partial step for this problem — especially for people who want to copy structured upgrade guidance into a coding agent workflow from the UI.

I don't think that fully closes the broader ask here yet, but it does mean there is movement happening in this area again.

It definitely feels like we're in the phase where people want coding agents to be able to support more and more of their upgrade workflow, so I wanted to make sure folks here knew this conversation is active again.