Package Exports
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@dfinity/service-worker) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
DFINITY Service Worker
Service worker which transforms browser asset request to the IC to canister calls and verifies the asset certification.
Build
| Usage | Folder | Command | Note |
|---|---|---|---|
| dev build for testnets | dist-dev | npm run build-dev |
- sets FORCE_FETCH_ROOT_KEY=1- not minified |
| prod build for mainnet | dist-prod | npm run build |
- uses IC root key - minified |
Prerequisites
- Node.js 17
- npm 8.5
Build With FORCE_FETCH_ROOT_KEY
By setting the FORCE_FETCH_ROOT_KEY=1 environment variable prior to building, the service worker will
always fetch the root key of the network before doing the validation.
THIS SHOULD ONLY BE USED ON A TEST OR LOCAL NETWORK. The IC mainnet public key is hard coded in the agent and, for security reasons, should not be fetched by the agent.
Develop
To start the local development instance:
- Run
npm install - Run
npm start
This will start serving the files built using npm run build-dev on http://localhost:8080. Any path that don't match a file instead will be sent to https://ic0.app.
Note that for the service worker to correctly relay the canister call to a canister there must be a query parameter canisterId=<canisterId>.
The service worker can be tested against any mainnet canister.
For example:
- Internet Identity: http://localhost:8080/?canisterId=rdmx6-jaaaa-aaaaa-aaadq-cai
- DSCVR: http://localhost:8080/?canisterId=h5aet-waaaa-aaaab-qaamq-cai
Developing locally on Safari
Safari does not allow service workers to be served on non-secure connections, even on localhost. So to test the service worker locally first follow the setup instructions on web.dev (except for the final step to generate SSL certs), then generate SSL certificates by running npm run create-ssl-certs. This will create self-signed certificates that will be stored in a temporary folder called certs. Now you can run npm run start-ssl. Now you can test using HTTPS.
For example:
- Internet Identity: https://localhost:8080/?canisterId=rdmx6-jaaaa-aaaaa-aaadq-cai
- DSCVR: https://localhost:8080/?canisterId=h5aet-waaaa-aaaab-qaamq-cai
Generating HTTP Gateway bindings
JavaScript binding
Generate the binding:
didc bind ./src/http-interface/canister_http_interface.did --target js > ./src/http-interface/canister_http_interface.jsThen move the StreamingCallbackHttpResponse variable outside of the idlFactory function, rename to streamingCallbackHttpResponseType and then export it.
export const streamingCallbackHttpResponseType = // ...and then add the import { IDL } from '@dfinity/candid'; import, move the Token variable outside of the idlFactory function, and set its value to be IDL.Unknown.
import { IDL } from '@dfinity/candid';
const Token = IDL.Unknown;TypeScript binding
Generate the binding:
didc bind ./src/http-interface/canister_http_interface.did --target ts > ./src/http-interface/canister_http_interface_types.d.tsAdd the following import:
import { IDL } from '@dfinity/candid';and then replace:
export type Token = { type: any };with:
export type Token = { type: <T>() => IDL.Type<T> };Testing locally
- Install mkcert.
brew install mkcert brew install nss # optional, for Firefox support
- Optionally, install the mkcert root CA
mkcert -install - Generate SSL certificates:
npm run create-ssl-certs - Add the following to your
/etc/hostsfile.127.0.0.1 ic0.local # Internet Identity 127.0.0.1 rdmx6-jaaaa-aaaaa-aaadq-cai.ic0.local 127.0.0.1 identity.ic0.local # NNS 127.0.0.1 qoctq-giaaa-aaaaa-aaaea-cai.ic0.local 127.0.0.1 nns.ic0.local # Distrikt 127.0.0.1 az5sd-cqaaa-aaaae-aaarq-cai.ic0.local 127.0.0.1 distrikt.ic0.local # Distrikt Staging 127.0.0.1 am2do-dyaaa-aaaae-aaasa-cai.ic0.local 127.0.0.1 distrikt-staging.ic0.local # DSCVR 127.0.0.1 h5aet-waaaa-aaaab-qaamq-cai.ic0.local 127.0.0.1 dscvr.ic0.local # Nuance 127.0.0.1 exwqn-uaaaa-aaaaf-qaeaa-cai.ic0.local 127.0.0.1 nuance.ic0.local
- Set the
hostnameCanisterIdMapvalue in thehttp_request.tsfile (make sure to revert this before commiting):const hostnameCanisterIdMap: Record<string, [string, string]> = { 'identity.ic0.local': ['rdmx6-jaaaa-aaaaa-aaadq-cai', 'ic0.app'], 'nns.ic0.local': ['qoctq-giaaa-aaaaa-aaaea-cai', 'ic0.app'], 'dscvr.ic0.local': ['h5aet-waaaa-aaaab-qaamq-cai', 'ic0.app'], 'distrikt.ic0.local': ['az5sd-cqaaa-aaaae-aaarq-cai', 'ic0.app'], 'distrikt-staging.ic0.local': ['am2do-dyaaa-aaaae-aaasa-cai', 'ic0.app'], 'nuance.ic0.local': ['exwqn-uaaaa-aaaaf-qaeaa-cai', 'ic0.app'], };
- Build and watch the service worker:
npm run build-dev -- --watch
- In a separate shell, build and run the docker image:
docker compose up - If you installed the root CA, that's all there is to do. If you chose not to install the root CA, then you will need to launch your browser with certain flags:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=/tmp/no-ssl --ignore-certificate-errors
Release
- Create MR that updates
versioninpackage.json - Test the built artifact using testnet boundary node VMs
- Merge MR to master
- Tag the commit on
masterwithservice-worker_v${version} - Verify that the desired version has been pushed to NPM: https://www.npmjs.com/package/@dfinity/service-worker
- Create an MR for the boundary nodes team that updates the
sw_versionandsw_sha256inic-os/boundary-guestos/rootfs/Dockerfile