Skip to content

fix: publish plugin-allure2 static assets in npm package - #783

Open
grootstebozewolf wants to merge 3 commits into
allure-framework:mainfrom
grootstebozewolf:fix/601-plugin-allure2-publish-static
Open

fix: publish plugin-allure2 static assets in npm package#783
grootstebozewolf wants to merge 3 commits into
allure-framework:mainfrom
grootstebozewolf:fix/601-plugin-allure2-publish-static

Conversation

@grootstebozewolf

Copy link
Copy Markdown

Summary

  • Include ./static in @allurereport/plugin-allure2 package.json files so published packages ship the template assets used at runtime.
  • Add a focused package-layout test covering publish contract + readTemplateManifest for single and multi modes.

Fixes #601

Context

Report generation resolves static/{single|multi}/manifest.json from the package root. With only ./dist published, npm installs hit ENOENT and only produce summary.json.

Test plan

  • npm pack --dry-run in packages/plugin-allure2 lists static/single/manifest.json and static/multi/manifest.json
  • yarn workspace @allurereport/plugin-allure2 test (package-layout tests pass)
  • allure generate with allure2 plugin (single + multi) produces index.html without ENOENT on static paths

Include ./static in the package files list so single- and multi-file
report generation can resolve template manifests after npm install.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

@allurereport/plugin-allure2 ships without static/ directory — report generation fails

1 participant