-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Major performance degrade after updating nuxt from 3.6.5
to 3.7
#216
Comments
Here are some additional tests I tried to check what it was that made my project so slow:
Now, when looking at the file Comparing this file generated before and after updating revealed, that the import statement of the packages is different. Before it was |
Moved the discussion to the nuxt repo nuxt/nuxt#25257 |
In a project of mine I updated the package nuxt from version 3.6.5 to 3.7.0 (bcc-code/bmm-web@3ecf83c) after which the performance of eslint degraded by a huge margin. What before was a matter of seconds, now took minutes!
I've chatted a bit in the nuxt forum, and one suggested that this might be an issue with this package.
I created a cpu profile of what was happening [...]
and narrowed it all down to a single vue-operation of my vue-file - a
v-for
expression (red in the picture above, focussed in the picture below).What was astonishing now was, that in here, I could see, that the function
createDiagnosticExplainingFile
, provided by typescript, was called more than once, and the first call took almost equally long before and after updating. But the fact, that after the update it was called multiple times for evaluating the onev-for
operation, was an explanation to be for this massive slow-down.Here's the file I was linting when creating the cpu profile: https://github.com/bcc-code/bmm-web/blob/3ecf83c1a8ea429acccf362fceaaf835e5bbce26/components/MediaPlayer.vue
EDIT: I found the issue #65, and my problem here has the exact same properties - it's slow when providing the parser-option
project
- but I couldn't confirm that the parserespree
or the packagetypescript-eslint-parser-for-extra-files
helped solving the issue.The text was updated successfully, but these errors were encountered: