Reorganized Dependencies by Removing Unused Packages and Placing in Correct Sections #72
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Natalia Luzuriaga <[email protected]>
Signed-off-by: Natalia Luzuriaga <[email protected]>
IsaacMilarky
approved these changes
Dec 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reorganized Dependencies by Removing Unused Packages and Placing in Correct Sections
Problem
We are no longer using Vite as our build tool for the frontend. Please refer to #61 for details on the new build tools we are using.
Currently, some dependencies in package.json are not placed in their correct sections.
UPDATE: This PR is similar to the closed #68 except this includes new dependencies needed for frontend code formatting and linting.
Solution
Removed
@11ty/eleventy-plugin-vitePlaced dependencies in their correct sections: dependencies vs devDependencies.
package-lock.jsonis updated accordingly as a result.Test Plan
No regression.
npm startandnpm run buildstill produce the website with the correct files and behaves the same.