SDK version 6 migration guide

This guide outlines the changes you need to make to your codebase to migrate from a version less than 6 of the Sleek SDK to version 6.

TL;DR

• Update the static files to new versions.
• Include the new t.js file at the root of your extension.
• Update the permissions field in the manifest to the new values, if required.
• Remove the content scripts from the manifest.

​

Static file changes

In previous versions of Sleek, the static files included were f.js and fc.js. Those files are now split into 3 files:

• f.js
• fc.js
• t.js

So, in addition to updating to the new version of the files, you should also include the new t.js file at the root of your extension.

​

Manifest JSON changes

​

permissions

In previous versions of the SDK, the permissions field in the manifest was set to:

alarms storage tabs webRequest webNavigation

The required permissions have changed, removing webRequest and adding scripting. So, the minimum permissions in your manifest.json should now be:

alarms storage tabs scripting webNavigation

​

Content scripts

In previous versions of the SDK, the content scripts were injected into the tab using the content_scripts field in the manifest. This is no longer necessary as the SDK now injects the content scripts itself.

Your extension manifest would have had a content_scripts field with the following:

"content_scripts": [
  ... your other content scripts,
  {
    all_frames: false,
    matches: ["<all_urls>"],
    run_at: "document_start",
    js: ["fc.js"],
  },
  {
    all_frames: true,
    matches: ["<all_urls>"],
    run_at: "document_idle",
    js: ["f.js"],
  }
]

The two content scripts should be removed from your extension manifest.

More detail:

For more detail on the changes, check out the updated installation guide.