If this release deserves a name, I would call it Brian aka @xt0rted. Brian's contributions are remarkable and I'm so grateful for his contributions and help. Thank you Brian!

PHP

Until now, support for PHP was limited to composer files. We want to change this! This release adds support for classes and functions that will link to their respective php.net page.

use ArrayAccess; // => https://www.php.net/manual/en/class.arrayaccess.php
use function preg_last_error; // => https://www.php.net/manual/en/function.preg-last-error.php

Added in #1033 by @stefanbuck

Paket

Paket is a dependency manager for .NET projects. OctoLinker links dependencies defined in paket.dependencies, paket.local or paket.references file like we do for package.json files.

nuget Chessie >= 0.6  // => https://www.nuget.org/packages/Chessie
github fsharp/FAKE modules/Octokit/Octokit.fsx // => https://github.com/fsharp/FAKE/blob/master/modules/Octokit/Octokit.fsx

Added in #1064 by @xt0rted

Other improvements

• Ruby require_relative fixes #1014 by @MatthewDG
• Add support for url() values in css #905 by @xt0rted
• Add support for docker hub actions #1024 by @xt0rted
• Support extensionless less imports #1034 by @xt0rted
• Exclude urls from css imports #1036 by @xt0rted

Housekeeping

• Rename dotnet packages for consistency #1051 by @vinmaster
• Update all repo urls to use main #1053 by @xt0rted
• Creating annotations for failed e2e tests #1063 by @xt0rted
• Add e2e test NOT annotation #1046 by @stefanbuck
• Ensure release note is updated #1050 by @stefanbuck

Like what we do?

Unlike many other browser extensions, OctoLinker is maintained and constantly updated since 2013. Please consider supporting our ongoing efforts. Thank you.

• @xt0rted Core contributor
• @stefanbuck Creator of OctoLinker

This release contains two improvements.

@xt0rted added better GitHub Actions support which adds links for local Actions in the current repo, as well as actions that have sub actions which are located in a sub folder for the given action #943

@stefanbuck worked on better OctoLinker notifications which is addressing #918 along with other improvements to make the notification less intrusive #975. Notifications will now appear in the bottom left corner in a new look and feel. Also dismissed, notification will be hidden for a period of time, if you're visiting a private repo without GitHub token or the token is invalid.

Unlike many other browser extensions, OctoLinker is maintained and constantly updated since 2013. Please consider supporting our ongoing efforts. Thank you.

• xt0rted Core contributor
• stefanbuck Creator of OctoLinker

---

All changes v6.4.0...v6.5.0

Svelte support + settings page with dark mode

Features

• Add support for .svelte files #898 by @xt0rted
• Add dark color scheme support in the options #895 by @fregante
• Track personal usage of OctoLinker #917 @stefanbuck

Housekeeping

• Drop CI env variable from GHA Workflow #896 by @fregante

All changes v6.3.0...v6.4.0

Like what we do? ❤️❤️❤️

Does OctoLinker make your life easier? Support us with a monthly donation.

• @xt0rted Core contributor
• @stefanbuck Creator of OctoLinker

Fix api.github.com permission

Fix

• Declare api.github.com as permission which was added to the wrong field in the mainfest file #894

Hovercard, Go Modules and new permission

New permission

As you might have been noticed, OctoLinker requires a new permission to access https://github.com. We explain in detail why this change was needed.

Highlight

We're thrilled to share this exciting new feature of OctoLinker with you. A hovercard that give you a sense of the linked GitHub repository. It holds the repository description, number of stars and forks, last update date and the primary language. Looks familiar, doesn't it? We borrowed this feature from GitHub.com. Check out #869 for implementation details.

Other improvements

• Support for Go Modules #879 by @StarpTech
• Support spaces in .net file paths #836

Housekeeping

• Use some shortcuts in the versioning script #866 by @fregante
• Bump prettier from 1.19.1 to 2.0.4 #873

All changes v6.2.2...v6.3.0

New extension permission

For details see https://github.com/OctoLinker/OctoLinker/issues/870

Bugfix

Unable to hide update notification #867

Cargo.toml support and other minor improvements

Features

• Add support for cargo.toml files #858 Thanks @xt0rted

Minor improvements

• Persist update notification on reload #839
• Add hint to disable OctoLinker for private repos #838

Bugfixes

• Do not pare suggested code changes block #837

Housekeeping

• Use relative resolver for nodejs plugin #840
• Various dependencies upgrades see all changes

All changes v6.1.0...v6.2.0

Bug fixes and much better .net support

Features

• Add support for .net references #808
• Add support for .net global tool configs #807
• Add support for .net project & file references #789

Bugfixes

• Fix linking of PR reviews comment #829
• Fix linking for duplicates in PR view #811

Housekeeping

• Bump actions/checkout from v1 to v2 #810
• Disable no-console warnings #809
• Add tests for plugin-dot-net-project #806

All changes v6.0.0...v6.1.0

Faster, better and more precisely than ever before

I'm extremely excited about today's release, but before we jump into the release notes for version 6 I want to welcome @xt0rted to the team. He has contributed several improvements ranging from bug fixes to adding .NET support and many other improvements. Welcome Brian 👋

What's new in v6

Originally this release was all about performance, but unintentionally it fixed other issues as well.

Back in June last year, @fregante opened an issue with the title "A script in the extension "OctoLinker" is causing Firefox to slow down". Until then, I wasn't aware OctoLinker was slow in Firefox.

OctoLinker uses a library called findAndReplaceDOMText which allows us to apply regular expression against the DOM and wraps each match with a link (now you know our secret sauce). Traversing the DOM for larger files took some time (especially on Firefox). In some circumstances, this even caused Firefox to freeze. This was caused by too many DOM lookups when applying the same regular expression over and over again to find keywords in the DOM.

DOM parsing in OctoLinker v5

DOM lookups are expensive and the root cause of this performance problem. Our solution to this is a new step before traversing the DOM. All regular expressions are performed against a string representation first followed by a very targeted DOM query to take online lines into account with a match. This speeds it up significantly.

DOM parsing in OctoLinker v6

This reduced the processing time by ~80% on large files and by ~30% for medium size files. In addition, we cap files to the first 5.000 lines to support enormous files with tens of thousand lines.

Other improvements

• OctoLinker now support for CODEOWNERS file #786
• Link dependencies in a package.json file with a version value of "latest" #791
• Expand .NET and nuget support #785 #787
• Link dependencies in a package.json file with a version value of gihtub:user/repo #794
• Link dependencies in a package.json file with a git url set as version value #793
• Improve UX when adding token through settings dialog #783

Bugfix

• Fix OctoLinker mascot position in notification bar #782
• Inconsistent linking when value appears on both sides of an assignment #618
• Package name in a js template literal disappears #590
• Commit comment elements are being parsed as dependencies and turned into links #454

Closing Thoughts

I am truly grateful to all the wonderful humans and companies supporting the development of OctoLinker. If you find OctoLinker useful, please consider donations through GitHub Sponsors or Open Collective – Thank you 🙇‍♂️