s-n-d-p/webclipper

The OneNote Web Clipper extension

WebClipper

Setup

1. Install npm -- https://nodejs.org/en/download/

(Note: on windows, you also need to add "%appdata%\npm" to your PATH)

2. Install the WebClipper packages

From the root of this project, run:

$ npm install

3. Build and Test

The default command to build and test:

$ npm run build
or
$ npm run build -- --<arg>

• Compiles LESS and TypeScript into /build
• Bundles the JavaScript modules together into /build/bundles
• Exports all the needed files to /target

4. Running in chrome

Google instructions

1. In chrome, open chrome://extensions/
2. Enable developer mode (upper right toggle)
3. Click on "load unpacked" and select the target/chrome folder
4. On subsequent builds, you don't have to go through this flow again. Simply refreshing the page should update the add-in

4. Running in edge

Microsoft instructions

1. In edge, go to edge://extensions
2. Enable developer mode (bottom left toggle)
3. Restart edge
4. Click on top right "...", then Extensions
5. Click on "Load unpacked" and select the target\edge\OneNoteWebClipper\edgeextension\manifest\extension
6. On subsequent builds, you need to go through steps (4) and (5) again

5. Looking at console output

Set the "enable_console_logging" local storage entry to true

6. Shipping an update to the store

Every store is different and you'll have to look at our internal guide to understand how to ship an update. In general, shipping in chrome/edge is easy and shipping in FF/Safari is hard. We don't ship any updates to IE anymore.

Edge

Instructions here

1. Build locally npm run build:prod
2. Run npm run pack-edge. The results will be in /OneNoteWebClipper/EdgeExtension
3. The file you will upload is the target/edge/OneNoteWebClipper/edgeextension/package/edgeExtension.appx file. You can also test by uploading the target/edge/onenotewebclipper/edgeextension/manifest/extension folder locally in edge
4. Now follow our internal instructions to update the package.

Congratulations!

At this point you should see the tests passing, and see the packaged code in the target folder

Other useful commands

Clean

$ npm run clean

Removes all of the generated files from build