-
Notifications
You must be signed in to change notification settings - Fork 68
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
Jiti 1.19.0 is broken with Cannot create property on string
#147
Comments
Having the same issue deploying a Shopify Hydrogen store with Oxygen |
Same for Nuxt 3 here |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Same here, using Svelte & Tailwind |
Hotfix added in |
Cannot create property on string
Works great, thanks @pi0 ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Nuxt 2 latest, Node 18
Reproduction
Seems to be present in Nuxt 2 minimal builds
Describe the bug
Nuxt 2 fails to start after upgrade to Jiti 1.19.0
Additional context
No response
Logs
Also CI/CD:
![image](https://private-user-images.githubusercontent.com/10450717/250911245-5107be7c-6cb6-4d26-8f60-19903aa65abe.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1MDM3MDcsIm5iZiI6MTczOTUwMzQwNywicGF0aCI6Ii8xMDQ1MDcxNy8yNTA5MTEyNDUtNTEwN2JlN2MtNmNiNi00ZDI2LThmNjAtMTk5MDNhYTY1YWJlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE0VDAzMjMyN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTliM2IyNGU1N2RmZWIwZTE5OGU2M2RjODk4Mjc2MjFlNGEwODE0NzViZGEyMWNjNDk3YTI5YWRjZWI2ZjdkYTMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.TH6v2uQ3omx6UeCwV29QdslxZ9dL9E3_2-X4F8CEISA)
The text was updated successfully, but these errors were encountered: