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

Initial migration to NextJS #268

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Initial migration to NextJS #268

wants to merge 6 commits into from

Conversation

technoph1le
Copy link
Owner

Description

We are migrating to NextJS before implementing the authentication and database storage system for each users. It will help us in the long term as QuickSnip starts to evolve.

Type of Change

  • ✨ New snippet
  • 🛠 Improvement to an existing snippet
  • 🐞 Bug fix
  • 📖 Documentation update
  • 🔧 Other (please describe): Code update

Checklist

  • I have tested my code and verified it works as expected.
  • My code follows the style and contribution guidelines of this project.
  • Comments are added where necessary for clarity.
  • Documentation has been updated (if applicable).
  • There are no new warnings or errors from my changes.

This is the initial draft, we will be making a lot of changes here. And, initial commit can have quite some errors until we fully and successfully migrate.

Related Issues

Closes #

Additional Context

Used this resource as a guide for migration from React Vite to NextJS: https://nextjs.org/docs/app/building-your-application/upgrading/from-vite

Screenshots (Optional)

Click to view screenshots

@technoph1le technoph1le added the enhancement New feature or request label Mar 12, 2025
package.json Outdated
"prismjs": "^1.29.0",
"react": "^18.3.1",
"react-dom": "^18.3.1",
"react-router-dom": "^7.1.1",
"react-syntax-highlighter": "^15.6.1"
"react-syntax-highlighter": "^5.8.0"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why did we rollback the react syntax highlighter version ?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting. It was done with npm audit fix. I guess, it was meant to be 15.8.0, but that is weird 🤔

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a reported vulnerability in the latest prismjs package version GHSA-x7hr-w5r2-h6wg. The npm audit fix sometimes recommends downgrading to avoid the vulnerability. I would recommend to keep the packages on their latest versions until a patch for prismjs is released.

@technoph1le technoph1le requested a review from majvax as a code owner March 17, 2025 10:38
Copy link
Collaborator

@Mathys-Gasnier Mathys-Gasnier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Btw why are we removing the workflows that check snippets formatting ?

@technoph1le
Copy link
Owner Author

Btw why are we removing the workflows that check snippets formatting ?

Not removing anything. Just importing all back one by one. :)

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

Successfully merging this pull request may close these issues.

3 participants