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
For a manual testing workflow, you should run `dev` and `storybook` at the same time.
32
+
33
+
## Testing local version elsewhere
34
+
35
+
You may configure a user package (like `amphtml`) to use your locally built version by using a [package path.](https://docs.npmjs.com/cli/v7/configuring-npm/package-json#local-paths)
36
+
37
+
### In [`ampproject/amphtml`](https://github.com/ampproject/amphtml/)
38
+
39
+
Point to a local copy on `build-system/tasks/storybook/package.json`. The following relative path has `amphtml/` and `storybook-addon-amp/` on the same level directory:
This way, you may use the local addon package's `npm run dev` in conjunction with `amp storybook` under `amphtml/`. Changes are picked up automatically.
@@ -57,3 +57,20 @@ The following parameters can be specified:
57
57
58
58
1.`extensions: [{name, version}]` - a list of extensions to be installed.
59
59
2.`experiments: [string]` - a list of experiments to enabled.
60
+
61
+
### `amp-script` hashes
62
+
63
+
Inline scripts used by `amp-script` require a `<meta name="amp-script-src">` tag that includes [their content hash](https://amp.dev/documentation/components/amp-script/#calculating-the-script-hash).
64
+
65
+
This addon generates the script hash for stories that need it. The following works without writing the respective `<meta>` tag:
0 commit comments