如何在Safari浏览器中安装自行开发的扩展程序？

Hey there! Great job getting your extension up and running smoothly on Chrome and Firefox—those are fantastic milestones. Now, when it comes to Safari, the process does have some notable differences from the other two browsers, largely due to Apple’s security sandboxing and developer requirements. Let’s break this down clearly so you can avoid missing key steps:

Core Differences from Chrome/Firefox #

• Mandatory Developer Account: Unlike Chrome/Firefox (where you can load unpacked extensions locally for free), Safari requires you to sign your extension with an Apple Developer Program membership (paid, ~$99/year) — even for personal testing. Unsigned extensions won’t load in modern Safari.
• Extension Packaging: Safari uses .safariextz packages, while Chrome/Firefox rely on .crx or standard WebExtension folders. Though Safari supports the WebExtensions API, you’ll need to convert or package your code using Apple’s tools.
• Hidden Developer Mode: Enabling developer features in Safari is less straightforward than in Chrome/Firefox, which is a common point of confusion.

Critical Steps to Install Your Custom Extension in Safari #

1. Enable Safari’s Developer Tools & Extension Support #

• Open Safari and navigate to Safari > Settings > Advanced
• Check the box labeled "Show Develop menu in menu bar" (this unlocks the tools you need)
• Next, go to Develop > Enable Extensions — this is an easy-to-miss step that’s required to load any custom extensions

2. Set Up Your Apple Developer Account #

• Sign up for the Apple Developer Program (if you haven’t already)
• Once logged in, generate a development certificate and provisioning profile for your extension. This is necessary to sign your code so Safari recognizes it as trusted.

3. Package & Sign Your Extension #

If your extension uses the standard WebExtensions API (which it should, since it works on Chrome/Firefox):

• Open Safari > Develop > Show Extension Builder
• Click the "+" button, select "Add Extension...", and choose your extension’s source folder
• Configure the extension details (name, permissions, website access) to match your Chrome/Firefox setup
• Click "Build" to create a .safariextz package, then sign it using your Apple Developer certificate directly in the Extension Builder

4. Install & Enable the Signed Extension #

• Double-click the .safariextz file — Safari will prompt you to confirm installation
• Navigate to Safari > Settings > Extensions to enable the extension and adjust any permission settings

Common Pitfalls to Avoid #

• Permission Mismatches: Safari is stricter with certain permissions (like fine-grained website access) than Chrome/Firefox. Double-check your manifest.json to ensure all permissions are declared correctly and are compatible with Safari’s WebExtensions support.
• API Gaps: While Safari supports most WebExtensions APIs, there are a few edge cases (e.g., some chrome.* specific methods aren’t fully implemented). You may need to add small polyfills or tweak your code for Safari compatibility.
• Testing Workflow: Instead of rebuilding the package every time you make changes, use the Extension Builder’s "Run" button to load the extension in development mode. This lets you test updates without repackaging and reinstalling repeatedly.

If you run into specific errors (like installation failures or unexpected permission prompts), feel free to share more details about your setup. But following these steps should cover the main differences and help you get your extension running in Safari.

内容的提问来源于stack exchange，提问作者Stefano Pozzi