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.
Please add relevant labels and merge
Thanks!
Description
Fix Project-wide ESLint Errors and Refactor Blog Data Structure
📌 Description
This PR resolves 27 linting errors and warnings identified across the project to improve code quality and build stability. It also includes a significant refactor of the Blog component to separate data from the UI, resolving "Fast Refresh" warnings.
Key Changes:
generateBlogPostsand large image imports fromcomponents/Blog.jsxto a dedicateddata/blogData.jsfile.src/data/blogData.jswith the actual data generation logic.useTheme,setHoveredPlan), and unnecessaryeslint-disabledirectives across multiple files (Navbar,Pricing,features,Login).eslint.config.jsto permit unused variables namedmotion(common in Framer Motion).vite.config.jsto correctly define__dirnamein an ES Module environment.useCallbackinAuthContextand fixed catch block syntax in utility files.🔗 Related Issue
Closes #254
🛠 Type of Change
✅ Checklist
🧪 Testing Done
npm run lintwhich now exits with code 0 (previously failed with 27 errors).Commands used: