| OLD | NEW |
| 1 <div id="pageData-name" class="pageData">Packaging</div> | 1 <div id="pageData-name" class="pageData">Packaging</div> |
| 2 <div id="pageData-showTOC" class="pageData">true</div> | 2 <div id="pageData-showTOC" class="pageData">true</div> |
| 3 | 3 |
| 4 <p> | 4 <p> |
| 5 This page describes how to package your extension. | 5 This page describes how to package your extension. |
| 6 As the <a href="overview.html">Overview</a> explains, | 6 As the <a href="overview.html">Overview</a> explains, |
| 7 extensions are packaged as signed ZIP files | 7 extensions are packaged as signed ZIP files |
| 8 with the file extension "crx" — | 8 with the file extension "crx" — |
| 9 for example, <code>myextension.crx</code>. | 9 for example, <code>myextension.crx</code>. |
| 10 </p> | 10 </p> |
| 11 | 11 |
| 12 <p> | 12 <p> |
| 13 <b>Note:</b> | 13 <b>Note:</b> |
| 14 You might not need to package your extension. | 14 You might not need to package your extension. |
| 15 If you publish your extension using the | 15 If you publish your extension using the |
| 16 <a href="https://chrome.google.com/extensions">gallery</a>, | 16 <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Develope
r Dashboard</a>, |
| 17 then the only reason to create your own <code>.crx</code> file | 17 then the only reason to create your own <code>.crx</code> file |
| 18 would be to distribute a non-public version — | 18 would be to distribute a non-public version — |
| 19 for example, to alpha testers. | 19 for example, to alpha testers. |
| 20 </p> | 20 </p> |
| 21 | 21 |
| 22 <!-- [PENDING: Refer to instructions on submitting an extension for inclusion in
the gallery.] --> | 22 <!-- [PENDING: Refer to instructions on submitting an extension for inclusion in
the gallery.] --> |
| 23 | 23 |
| 24 <p> | 24 <p> |
| 25 When you package an extension, | 25 When you package an extension, |
| 26 the extension is assigned a unique key pair. | 26 the extension is assigned a unique key pair. |
| (...skipping 45 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 72 </ol> | 72 </ol> |
| 73 | 73 |
| 74 | 74 |
| 75 <p> | 75 <p> |
| 76 <b>Do not lose the private key!</b> | 76 <b>Do not lose the private key!</b> |
| 77 Keep the <code>.pem</code> file secret and in a safe place. | 77 Keep the <code>.pem</code> file secret and in a safe place. |
| 78 You'll need it later if you want to do any of the following: | 78 You'll need it later if you want to do any of the following: |
| 79 </p> | 79 </p> |
| 80 <ul> | 80 <ul> |
| 81 <li><a href="#update">Update</a> the extension</li> | 81 <li><a href="#update">Update</a> the extension</li> |
| 82 <li>Upload the extension to the | 82 <li>Upload the extension using the |
| 83 <a href="https://chrome.google.com/extensions">Extensions Gallery</a> </li> | 83 <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Develope
r Dashboard</a></li> |
| 84 </ul> | 84 </ul> |
| 85 | 85 |
| 86 <p> | 86 <p> |
| 87 If the extension is successfully packaged, you'll see a dialog like this | 87 If the extension is successfully packaged, you'll see a dialog like this |
| 88 that tells you where to find | 88 that tells you where to find |
| 89 the <code>.crx</code> and <code>.pem</code> files:</p> | 89 the <code>.crx</code> and <code>.pem</code> files:</p> |
| 90 </p> | 90 </p> |
| 91 | 91 |
| 92 <img src="images/package-success.gif" | 92 <img src="images/package-success.gif" |
| 93 width="554" height="208" /> | 93 width="554" height="208" /> |
| (...skipping 58 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 152 | 152 |
| 153 <p> | 153 <p> |
| 154 To suppress the dialog, | 154 To suppress the dialog, |
| 155 add <code>--no-message-box</code> to the command. | 155 add <code>--no-message-box</code> to the command. |
| 156 </p> | 156 </p> |
| 157 | 157 |
| 158 <h2>Package format and scripts</h2> | 158 <h2>Package format and scripts</h2> |
| 159 <p> | 159 <p> |
| 160 For more information on the format, as well as pointers to scripts you can use | 160 For more information on the format, as well as pointers to scripts you can use |
| 161 to create <code>.crx</code> files, see <a href="crx.html">CRX package format</a>
. | 161 to create <code>.crx</code> files, see <a href="crx.html">CRX package format</a>
. |
| 162 </p> | 162 </p> |
| OLD | NEW |