fix: use plugin source in example to avoid type mismatches #442
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

TL;DR
Updated the example project to use the local plugin version instead of the published one.
What changed?
Modified the example project's package.json and package-lock.json to use the local plugin version (
file:..) instead of the published version (^2.4.1). This links the example project to the local development version of the plugin.How to test?
npm installin the example directorynpm run devWhy make this change?
This change enables easier development and testing of the plugin by allowing developers to see their changes immediately reflected in the example project without having to publish new versions. It creates a direct link between the plugin source code and the example implementation, streamlining the development workflow.