Nuxt: Broken since 0.0.35 #1716
Assignees
Labels
bug
Something isn't working
Comments
|
Hello @max06 thanks for reporting the issue! We are on the case 🔍 . In the meanwhile, I think version |
|
Hey @amritk - thanks for the headsup! 0.0.34 is also working fine, just in case. Based on the commit history 0.0.35 looked like it could cause issues so I started testing at 0.0.34 - lucky hit 🍀 |
|
hmm strange, because I found another issue in 0.0.34. Could be that the issue is only in dev |
|
Good to know, I'll keep my eyes open! 🙇🏼 |
|
On it! :) 0.0.33, 0.0.32 and 0.0.31 aren’t on npm (because our release workflow was broken) language "json" has no grammar.scalar/scalar@main gives me:
debug does not provide export named defaultFresh Nuxt project, as soon as I scroll I get the following error for all versions: |
This was referenced May 14, 2024
marclave
pushed a commit
that referenced
this issue
May 16, 2024
…#1746) * refactor: use lowlight for syntax highlighting in markdown * docs(changeset): refactor: use lowlight instead of prism in the markdown component (rollback 64024a5) * fix: nuxt route on start page * test: nuxt playwright testing and remove broken nuxt unit tests * chore: fix nuxt test workflow * chore: fix testing workflow --------- Co-authored-by: Amrit <[email protected]> Co-authored-by: tmastrom <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happens?
The requested module '/_nuxt/@fs/workspaces/nimbus/node_modules/boolbase/index.js?v=c13543d7' does not provide an export named 'default'This did not break in 0.0.34.
What did you expect to happen?
It should not break
How can we reproduce the issue?
bun add @scalar/[email protected])Swagger/OpenAPI Example
No response
The text was updated successfully, but these errors were encountered: