-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
development mode and build mode instrument result is different in normal web project #89
Comments
iFaxity
added a commit
that referenced
this issue
Feb 17, 2024
…es (#180) * fix: add regex for vue SFC to prevent instrumenting style and templates Single file Components no longer have their html or css instrumented instead of their script Closes #96 #178 #89 * build: add prepare script to build the package when using a git version See https://stackoverflow.com/a/57829251 * build: fix dependencies' vulnerabilities run npm audit fix * build: bump devDependencies (patch version only) * fix: instrument both option and composition API * style: fix sonarlint issues * revert: reverted changes to dependencies and package.json Refs: 1e67efc, ea8fa18, 614a88a * style: changed to single quotes for strings --------- Co-authored-by: Hugo <hugo.daclon@etu.univ-nantes.fr> Co-authored-by: Christian Norrman <christian@faxity.se>
Hi @calmzhuang, Could you please try the new rc version released with #180 if this fixes your issue? |
Closing until this conversation gets picked up again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
development mode and build mode instrument result is different in normal web project
development mode:
build mode:
Binaries:
node: v14.18.2
npm: 6.14.15
vite-plugin-istanbul:4.0.1
Browsers:
Chromium (111.0.5563.110)
Used Package Manager
npm
Logs
No response
The text was updated successfully, but these errors were encountered: