You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/contributing/Build-XKit.md
+37-4Lines changed: 37 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,9 +10,38 @@
10
10
11
11
Serving extensions and themes locally is useful for rapid development without requiring the use of the XKit Editor, but some initial set up is required:
12
12
13
-
1. Run `gulp server` to start the resource server. This task will automatically build the extension and theme files from source before the server starts. See [`gulp server`](#gulp-server) for more information.
14
-
2. Navigate to `https://localhost:31337` and create a security exception for the `localhost` domain. The project uses self-signed SSL/TLS certificates that are untrusted by default in order to work around mixed-content warnings for websites like Tumblr that are served over HTTPS.
15
-
3. Change [the relevant lines](https://gist.github.com/hobinjk/4b0ae4698d4e35320d3c977753946cf5) in xkit.js and manifest.json to point to and allow serving XKit from `localhost`.
13
+
1. Run `npm run watch-extensions` to start the resource server. This task will automatically build the extension and theme files from source whenever they are changed, storing them in `Extensions/dist`.
14
+
2. Change these lines in xkit.js and manifest.json to point the XKit updater at `Extensions/dist`:
0 commit comments