This PR introduces changes required for scaffolding new plugins with plugin-e2e and playwright.
On scaffold create-plugin now scaffolds a plugin with playwright configured out the box and sample integration tests.
On update create-plugin checks if there is either the usePlaywright feature flag set OR a playwright config file (playwright.config.ts) in the root of the project to decide on which dependencies and scripts should be used.
Tests across various package managers and the github workflow changes can be found in this temporary repo.
Hello! 👋 This repository uses Auto for releasing packages using PR labels.
✨ This PR can be merged and will trigger a new minor release.
NOTE: When merging a PR with the release label please avoid merging another PR. For further information see here.
What this PR does / why we need it:
This PR introduces changes required for scaffolding new plugins with plugin-e2e and playwright.
usePlaywright
feature flag set OR a playwright config file (playwright.config.ts
) in the root of the project to decide on which dependencies and scripts should be used.Tests across various package managers and the github workflow changes can be found in this temporary repo.
Which issue(s) this PR fixes:
Fixes https://github.com/grafana/grafana-plugins-platform-team/issues/106
Special notes for your reviewer:
📦 Published PR as canary version:
Canary Versions
:sparkles: Test out this PR locally via: ```bash npm install @grafana/create-plugin@4.5.0-canary.847.62129f3.0 npm install @grafana/plugin-e2e@0.27.0-canary.847.62129f3.0 # or yarn add @grafana/create-plugin@4.5.0-canary.847.62129f3.0 yarn add @grafana/plugin-e2e@0.27.0-canary.847.62129f3.0 ```