Create nuxtjs.yml

[Dargon789]

Summary by Sourcery

Add GitHub Actions workflow for deploying a Nuxt.js site to GitHub Pages

New Features:

• Add support for automatic detection of package manager (npm or yarn)
• Set up Node.js environment with version 20

CI:

• Create a comprehensive GitHub Actions workflow for automatic Nuxt.js site deployment

Deployment:

• Configure automatic static site generation and deployment to GitHub Pages

[sourcery-ai]

Reviewer's Guide

This PR implements an automated CI/CD pipeline for Nuxt.js applications by adding a new GitHub Actions workflow file, .github/workflows/nuxtjs.yml. The workflow is designed to build the static site and deploy it to GitHub Pages, triggered by pushes to the main branch or manually.

File-Level Changes

Change	Details	Files
Added GitHub Actions workflow for automated Nuxt.js deployment to GitHub Pages.	Configured workflow triggers for main branch pushes and manual workflow_dispatch. Set GITHUB_TOKEN permissions required for GitHub Pages deployment. Established concurrency control for the pages deployment group to manage simultaneous runs. Defined a build job that checks out code, sets up the Node.js environment, detects the package manager, installs dependencies, generates the Nuxt static site, and uploads the build artifact. Defined a deploy job that depends on the successful completion of the build job and deploys the artifact to GitHub Pages.	.github/workflows/nuxtjs.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 46 minutes (more than 100, code: "api-deployments-free-per-day").

[sourcery-ai]

Hey @Dargon789 - I've reviewed your changes - here's some feedback:

• Consider basing the .nuxt cache key on source file hashes (e.g., lockfiles, nuxt.config.js) instead of hashFiles('dist') for improved accuracy and effectiveness.
• The package manager detection script should check for package-lock.json when intending to use npm ci, or use npm install as a fallback if package-lock.json is absent.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}