{"_id":"4094fixer","_rev":"2-7ba4d9568dbc74dc553d46b57cdf8e9a","name":"4094fixer","dist-tags":{"latest":"1.0.4"},"versions":{"1.0.0":{"name":"4094fixer","version":"1.0.0","keywords":["nextjs","error-fix","4094","clear-cache","node_modules","nextjs 4094 error","nextjs error fix","next.js troubleshooting","cache clearing","nextjs restart","nextjs dependency reinstall","nextjs development"],"author":{"name":"kimjusnu"},"license":"ISC","_id":"4094fixer@1.0.0","maintainers":[{"name":"kimjunsu","email":"junsu4621@naver.com"}],"dist":{"shasum":"642d2f4395854fd2a41b284d241df6f2ed76046f","tarball":"https://registry.npmjs.org/4094fixer/-/4094fixer-1.0.0.tgz","fileCount":4,"integrity":"sha512-Sfz2wy7TsKsZdUUbWtz33aYsmh0/P1Twpafv2Iy9i8NOpy4fIxzXOEhzEFRS1o7DMPS1m58aQ5NU8c8n60Exmw==","signatures":[{"sig":"MEQCIAKUBScpFLd6IT8bhKxiUug67YEQ90X5x4YceVP6C4WbAiA0v+WQ9T7P0GsyYxSlxW/IaRqFzKD0w2d0e5x+iTJj4A==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":6177},"main":"index.js","gitHead":"9e6a963798e60411618e553c8c6fcb491d2adf12","scripts":{"dev":"next dev","clear4094":"node scripts/clear4094.js"},"_npmUser":{"name":"kimjunsu","email":"junsu4621@naver.com"},"_npmVersion":"10.8.2","description":"Automatically detects and fixes the 4094 error in Next.js by clearing cache, reinstalling dependencies, and restarting the development server.","directories":{},"_nodeVersion":"20.12.0","_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/4094fixer_1.0.0_1728283145952_0.9648166841240244","host":"s3://npm-registry-packages"}},"1.0.2":{"name":"4094fixer","version":"1.0.2","keywords":["nextjs","error-fix","4094","clear-cache","node_modules","nextjs 4094 error","nextjs error fix","next.js troubleshooting","cache clearing","nextjs restart","nextjs dependency reinstall","nextjs development"],"author":{"name":"kimjusnu"},"license":"ISC","_id":"4094fixer@1.0.2","maintainers":[{"name":"kimjunsu","email":"junsu4621@naver.com"}],"bin":{"clear4094":"scripts/clear4094.js"},"dist":{"shasum":"89942afdfef2629e9d687d778dba5c18e079bd6d","tarball":"https://registry.npmjs.org/4094fixer/-/4094fixer-1.0.2.tgz","fileCount":4,"integrity":"sha512-8JmWP5/GnIH82gH7iyMxBAKbnOLHa9Hvcu23owUugTv7lOe5MUvzQv4oWujfFAIxI0zpNXWEp0ot5ZBPNHx4ZA==","signatures":[{"sig":"MEUCIEWNl3Ihyff+rYQzrC0AN+sPFDG3p6T76+/9DJCrZlDEAiEAiUK6AM8mJhZK7fwwoxhYWfPfE9xrZZ9MsVS+J0v9EeI=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":6238},"main":"index.js","gitHead":"1ee7f9489cca4744869f3b2c8c8079c4debf095a","scripts":{"dev":"next dev","clear4094":"node scripts/clear4094.js"},"_npmUser":{"name":"kimjunsu","email":"junsu4621@naver.com"},"_npmVersion":"10.8.2","description":"Automatically detects and fixes the 4094 error in Next.js by clearing cache, reinstalling dependencies, and restarting the development server.","directories":{},"_nodeVersion":"20.12.0","_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/4094fixer_1.0.2_1728284024996_0.33127825940079014","host":"s3://npm-registry-packages"}},"1.0.4":{"name":"4094fixer","version":"1.0.4","description":"Automatically detects and fixes the 4094 error in Next.js by clearing cache, reinstalling dependencies, and restarting the development server.","main":"index.js","bin":{"clear4094":"scripts/clear4094.js"},"scripts":{"dev":"next dev","clear4094":"node scripts/clear4094.js"},"keywords":["nextjs","error-fix","4094","clear-cache","node_modules","nextjs 4094 error","nextjs error fix","next.js troubleshooting","cache clearing","nextjs restart","nextjs dependency reinstall","nextjs development"],"author":{"name":"kimjusnu"},"license":"ISC","dependencies":{"next":"^14.2.14","yarn":"^1.22.22"},"_id":"4094fixer@1.0.4","gitHead":"b59ac34d7856e2adada2b99d05e3029b2ef03bfb","_nodeVersion":"20.12.0","_npmVersion":"10.8.2","dist":{"integrity":"sha512-sr8hQ82hr4avMdCTnZn8Rg11ufHP1N8LKq9UgUXSpSvf+hN15/XwwTnOygies8USCTEdEEctTMbEq8LlVkNrfg==","shasum":"aaab0179f3491639be74124e7baa00990a82cdef","tarball":"https://registry.npmjs.org/4094fixer/-/4094fixer-1.0.4.tgz","fileCount":3,"unpackedSize":4427,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGeA4mq1GiPNjIWh6FhpeuyrH/uHvZyJ5XZK/htm4SnKAiEArByTqZqcdR7CvP2QKF7B8/dDaspEGrmi65WoolzgQfw="}]},"_npmUser":{"name":"kimjunsu","email":"junsu4621@naver.com"},"directories":{},"maintainers":[{"name":"kimjunsu","email":"junsu4621@naver.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/4094fixer_1.0.4_1728296579606_0.8117208703594598"},"_hasShrinkwrap":false}},"time":{"created":"2024-10-07T06:39:05.828Z","modified":"2024-10-07T10:22:59.927Z","1.0.0":"2024-10-07T06:39:06.122Z","1.0.2":"2024-10-07T06:53:45.232Z","1.0.4":"2024-10-07T10:22:59.758Z"},"author":{"name":"kimjusnu"},"license":"ISC","keywords":["nextjs","error-fix","4094","clear-cache","node_modules","nextjs 4094 error","nextjs error fix","next.js troubleshooting","cache clearing","nextjs restart","nextjs dependency reinstall","nextjs development"],"description":"Automatically detects and fixes the 4094 error in Next.js by clearing cache, reinstalling dependencies, and restarting the development server.","maintainers":[{"name":"kimjunsu","email":"junsu4621@naver.com"}],"readme":"# 4094Fixer 🚀\r\n\r\n**Resolve Next.js 4094 errors with automatic cache clearing and package reinstalling.**\r\n\r\n## Overview ✨\r\n\r\n`4094Fixer` is a simple yet powerful tool designed to automatically tackle the dreaded 4094 error that can sometimes pop up in Next.js projects. Instead of manually clearing caches and reinstalling packages every time, let `4094Fixer` handle all the grunt work while you focus on building amazing things. 💡\r\n\r\n### Features 🛠️\r\n\r\n- **Automatic 4094 Error Detection**: Instantly catches the pesky 4094 error as soon as it occurs.\r\n- **Cache Cleanup**: Wipes out the `.next` build cache, `node_modules`, and `yarn.lock` (or `package-lock.json` for npm users).\r\n- **Quick Reinstall**: Automatically reinstalls all the dependencies and restarts your development server, so you don’t have to!\r\n- **Works with Both Yarn and NPM**: Doesn’t matter what package manager you’re using – we’ve got you covered. 😉\r\n\r\n---\r\n\r\n## Installation 📦\r\n\r\n1. **Clone the repository:**\r\n\r\n   ```bash\r\n   git clone https://github.com/yourusername/4094Fixer.git\r\n   cd 4094Fixer\r\n   ```\r\n\r\n2. Install dependencies:\r\n\r\n   If using `yarn`:\r\n\r\n   ```bash\r\n   yarn install\r\n   ```\r\n\r\n   If using `npm`:\r\n\r\n   ```bash\r\n   npm install\r\n   ```\r\n\r\n---\r\n\r\n## Usage🖥️\r\n\r\n1. **Run the Fixer**:\r\n\r\n   If you're using `yarn`:\r\n\r\n   ```bash\r\n   yarn clear4094\r\n   ```\r\n\r\n   If you're using `npm`:\r\n\r\n   ```bash\r\n   npm run clear4094\r\n   ```\r\n\r\n   This magical command will detect the 4094 error, clear all the necessary caches, reinstall the packages, and restart your server. Easy peasy, lemon squeezy! 🍋\r\n\r\n---\r\n\r\n## How It Works 🔧\r\n\r\nHere’s what happens under the hood when `4094Fixer` works its magic:\r\n\r\n### Cache Cleanup 🧹\r\n\r\nDeletes the following directories and files:\r\n\r\n- `.next/` directory (Next.js build cache)\r\n- `node_modules/` directory (installed dependencies)\r\n- `yarn.lock` or `package-lock.json` (depending on your package manager)\r\n\r\n### Package Reinstallation 📦\r\n\r\nOnce the cleanup is complete, it reinstalls the necessary packages using `yarn install` or `npm install`.\r\n\r\n### Server Restart 🚀\r\n\r\nAfter everything is back in place, it automatically restarts the Next.js development server (`yarn dev` or `npm run dev`).\r\n\r\n---\r\n\r\n## Example Workflow\r\n\r\n1. You're working on a Next.js project and suddenly encounter the 4094 error.\r\n2. Run the `clear4094` command (using `yarn` or `npm`).\r\n3. The cache is cleared, dependencies are reinstalled, and the server is restarted automatically.\r\n4. Continue developing without having to manually fix the 4094 error!😊\r\n","readmeFilename":"README.md"}