Skip to content
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

fix(deps): update @nuxt/scripts to v0.10.1 #373

Merged
merged 2 commits into from
Feb 8, 2025
Merged

Conversation

dargmuesli
Copy link
Collaborator

@dargmuesli dargmuesli commented Feb 8, 2025

πŸ”— Linked issue

n/a

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

Nuxt Scripts v0.10.0 changed the alias path and this PR updates them here.

@dargmuesli dargmuesli force-pushed the fix/deps/scripts-v0.10 branch from 282cdee to 3c8aa44 Compare February 8, 2025 18:36
package.json Outdated Show resolved Hide resolved
Co-authored-by: Daniel Roe <[email protected]>
@danielroe danielroe changed the title fix(deps): update @nuxt/scripts to v0.10.1 fix(deps): update @nuxt/scripts to v0.10.1 Feb 8, 2025
@danielroe danielroe merged commit 1ffe504 into main Feb 8, 2025
4 checks passed
@danielroe danielroe deleted the fix/deps/scripts-v0.10 branch February 8, 2025 22:02
dargmuesli-bot pushed a commit that referenced this pull request Feb 8, 2025
## [0.9.12](v0.9.11...v0.9.12) (2025-02-08)

### Bug Fixes

* **deps:** update `@nuxt/scripts` to v0.10.1 ([#373](#373)) ([1ffe504](1ffe504))
@dargmuesli-bot
Copy link
Collaborator

πŸŽ‰ This PR is included in version 0.9.12 πŸŽ‰

The release is available on:

Your semantic-release bot πŸ“¦πŸš€

@harlan-zw
Copy link

Oops sorry, I will avoid modifying these paths in the future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants