Skip to content

Conversation

@transcript-js
Copy link

Tested the suggestion of @siilike, solves #28.
I would be happy not to rely on this local fix :​)

@greg-szrama
Copy link

@tsironis I really need this fix as well and I'd like to keep synced with the official repository for maintenance purposes. Can we get a new patch release with this in it?

@vtlim
Copy link

vtlim commented Jul 17, 2025

+1 would love to see this fix go in

@wojsmol
Copy link

wojsmol commented Nov 11, 2025

@tsironis Any chance to ship it in a release?

@SHxKM
Copy link

SHxKM commented Nov 12, 2025

This is also affecting us.

@transcript-js
Copy link
Author

Apologies that I didn't catch up here. After submitting my PR I've noticed that the problem still persists after the build process.
So, I decided to write a new plugin which is based on the same ideas but doesn't rely on webpack and uses a more robust handling of the terms' links. I haven't published this, yet but I'm willing to share the code (compatible and tested with Docusaurus 3.7.0.) in advance and without any warranty. Disclaimer: I'm using this in production for a client's project -- but it's not a public one (authorization needed).

@wojsmol
Copy link

wojsmol commented Nov 12, 2025

@transcript-js This fix is working on postinstall - see #28 (comment)

@transcript-js
Copy link
Author

@wojsmol Ah, I'll probably give this a try -- but to be honest, I'm absolutely fine with my solution. Especially for dropping the Webpack dependency 😬 (less dependencies and a lot smaller as well).
But thx for taking care at least! ❤️
(and I guess I need to take the time for publishing my plugin 😅 )

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.

5 participants