| OLD | NEW |
| 1 <div id="pageData-name" class="pageData">Packaging</div> | 1 <h1>Packaging</h1> |
| 2 <div id="pageData-showTOC" class="pageData">true</div> | 2 |
| 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"—for example, | 8 with the file extension "crx"—for example, |
| 9 <code>myextension.crx</code>. | 9 <code>myextension.crx</code>. |
| 10 </p> | 10 </p> |
| 11 | 11 |
| 12 <p> | 12 <p> |
| (...skipping 69 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 82 <li><a href="#update">Update</a> the extension</li> | 82 <li><a href="#update">Update</a> the extension</li> |
| 83 <li><a href="#upload">Upload</a> the extension to the Chrome Web Store</li> | 83 <li><a href="#upload">Upload</a> the extension to the Chrome Web Store</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="{{static}}/images/package-success.gif" |
| 93 width="554" height="208" /> | 93 width="554" height="208" /> |
| 94 | 94 |
| 95 | 95 |
| 96 <h2 id="update">Updating a package</h2> | 96 <h2 id="update">Updating a package</h2> |
| 97 | 97 |
| 98 <p>To create an updated version of your extension:</p> | 98 <p>To create an updated version of your extension:</p> |
| 99 <ol> | 99 <ol> |
| 100 <li> | 100 <li> |
| 101 Increase the version number in <code>manifest.json</code>. | 101 Increase the version number in <code>manifest.json</code>. |
| 102 </li> | 102 </li> |
| (...skipping 21 matching lines...) Expand all Loading... |
| 124 example, <code>c:\myext.pem</code>. | 124 example, <code>c:\myext.pem</code>. |
| 125 </li> | 125 </li> |
| 126 | 126 |
| 127 <li> | 127 <li> |
| 128 Click <b>OK</b>. | 128 Click <b>OK</b>. |
| 129 </li> | 129 </li> |
| 130 </ol> | 130 </ol> |
| 131 | 131 |
| 132 <p>If the updated extension is successfully packaged, you'll see a dialog like t
his:</p> | 132 <p>If the updated extension is successfully packaged, you'll see a dialog like t
his:</p> |
| 133 | 133 |
| 134 <img src="../images/update-success.gif" | 134 <img src="{{static}}/images/update-success.gif" |
| 135 width="298" height="160" /> | 135 width="298" height="160" /> |
| 136 | 136 |
| 137 | 137 |
| 138 <h2 id="upload"> Uploading a previously packaged extension to the Chrome Web Sto
re</h2> | 138 <h2 id="upload"> Uploading a previously packaged extension to the Chrome Web Sto
re</h2> |
| 139 | 139 |
| 140 <p> | 140 <p> |
| 141 You can use the Chrome Developer Dashboard | 141 You can use the Chrome Developer Dashboard |
| 142 to upload an extension that you've previously packaged yourself. | 142 to upload an extension that you've previously packaged yourself. |
| 143 However, unless you take special steps, | 143 However, unless you take special steps, |
| 144 the extension's ID in the Chrome Web Store | 144 the extension's ID in the Chrome Web Store |
| (...skipping 38 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 183 | 183 |
| 184 <p> | 184 <p> |
| 185 To suppress the dialog, | 185 To suppress the dialog, |
| 186 add <code>--no-message-box</code> to the command. | 186 add <code>--no-message-box</code> to the command. |
| 187 </p> | 187 </p> |
| 188 | 188 |
| 189 <h2>Package format and scripts</h2> | 189 <h2>Package format and scripts</h2> |
| 190 <p> | 190 <p> |
| 191 For more information on the format, as well as pointers to scripts you can use | 191 For more information on the format, as well as pointers to scripts you can use |
| 192 to create <code>.crx</code> files, see <a href="crx.html">CRX Package Format</a>
. | 192 to create <code>.crx</code> files, see <a href="crx.html">CRX Package Format</a>
. |
| 193 </p> | 193 </p> |
| OLD | NEW |