kenmirrors/MagicMirror
1
0
Fork 0
mirror of https://github.com/MichMich/MagicMirror.git synced 2026-06-03 18:00:33 +00:00
Code Issues Projects Releases Wiki Activity
Files
9386c44928d5b8a930daa8cfd0caeee35500a4c7
MagicMirror/package.json

144 lines
4.2 KiB
JSON
Raw Normal View History

Added electron wrapper
2016-03-27 20:40:07 +02:00
{
Add pretty-quick
2020-05-11 21:59:45 +02:00
"name": "magicmirror",
update version in package.json
2026-04-30 22:55:47 +02:00
"version": "2.37.0-develop",
Add pretty-quick
2020-05-11 21:59:45 +02:00
"description": "The open source modular smart mirror platform.",
Update deps (#3439) - update dependencies including electron to v30 - replace node v21 with v22 in tests
2024-05-01 19:54:38 +02:00
"keywords": [
"magic mirror",
"magicmirror",
"smart mirror",
"mirror UI",
"modular"
],
"homepage": "https://magicmirror.builders",
"bugs": {
"url": "https://github.com/MagicMirrorOrg/MagicMirror/issues"
},
"repository": {
"type": "git",
"url": "https://github.com/MagicMirrorOrg/MagicMirror"
},
"license": "MIT",
"author": "Michael Teeuw",
"contributors": [
[core] bump dependencies into december (#3982) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: veeck <gitkraken@veeck.de> Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com>
2025-12-01 20:05:06 +01:00
{
"name": "MagicMirror contributors",
"url": "https://github.com/MagicMirrorOrg/MagicMirror/graphs/contributors"
}
Update deps (#3439) - update dependencies including electron to v30 - replace node v21 with v22 in tests
2024-05-01 19:54:38 +02:00
],
Update package type to `commonjs` (#3814) related to #3804 added type to `commonjs` in package.json
2025-06-20 14:26:33 +02:00
"type": "commonjs",
refactor default modules: move scheduleTimer to one place (#3837) see #3819 --------- Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com> Co-authored-by: Veeck <github@veeck.de>
2025-07-10 08:12:09 +02:00
"imports": {
Make `User-Agent` configurable (#3255) Fixes #3253 Adds a configuration option to overwrite the default `User-Agent` header that is send at least by the calendar and news module. Allows other modules to use the individual user agent as well. The configuration accepts either a string or a function: ``` var config = { ... userAgent: 'Mozilla/5.0 (My User Agent)', ... } ``` or ``` var config = { ... userAgent: () => 'Mozilla/5.0 (My User Agent)', ... } ``` --------- Co-authored-by: Veeck <github@veeck.de> Co-authored-by: veeck <gitkraken@veeck.de> Co-authored-by: Karsten Hassel <hassel@gmx.de> Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com>
2025-08-27 13:50:37 +02:00
"#server_functions": {
"default": "./js/server_functions.js"
[core] refactor: extract and centralize HTTP fetcher (#4016) ## Summary PR [#3976](https://github.com/MagicMirrorOrg/MagicMirror/pull/3976) introduced smart HTTP error handling for the Calendar module. This PR extracts that HTTP logic into a central `HTTPFetcher` class. Calendar is the first module to use it. Follow-up PRs would migrate Newsfeed and maybe even Weather. **Before this change:** - ❌ Each module had to implemented its own `fetch()` calls - ❌ No centralized retry logic or backoff strategies - ❌ No timeout handling for hanging requests - ❌ Error detection relied on fragile string parsing **What this PR adds:** - ✅ Unified HTTPFetcher class with intelligent retry strategies - ✅ Modern AbortController with configurable timeout (default 30s) - ✅ Proper undici Agent for self-signed certificates - ✅ Structured error objects with translation keys - ✅ Calendar module migrated as first consumer - ✅ Comprehensive unit tests with msw (Mock Service Worker) ## Architecture **Before - Decentralized HTTP handling:** ``` Calendar Module Newsfeed Module Weather Module ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │ fetch() own │ │ fetch() own │ │ fetch() own │ │ retry logic │ │ basic error │ │ no retry │ │ error parse │ │ handling │ │ client-side │ └─────────────┘ └─────────────┘ └─────────────┘ │ │ │ └───────────────────────┴───────────────────────┘ ▼ External APIs ``` **After - Centralized with HTTPFetcher:** ``` ┌─────────────────────────────────────────────────────┐ │ HTTPFetcher │ │ • Unified retry strategies (401/403, 429, 5xx) │ │ • AbortController timeout (30s) │ │ • Structured errors with translation keys │ │ • undici Agent for self-signed certs │ └────────────┬──────────────┬──────────────┬──────────┘ │ │ │ ┌───────▼───────┐ ┌────▼─────┐ ┌──────▼──────┐ │ Calendar │ │ Newsfeed │ │ Weather │ │ ✅ This PR │ │ future │ │ future │ └───────────────┘ └──────────┘ └─────────────┘ │ │ │ └──────────────┴──────────────┘ ▼ External APIs ``` ## Complexity Considerations **Does HTTPFetcher add complexity?** Even if it may look more complex, it actually **reduces overall complexity**: - **Calendar already has this logic** (PR #3976) - we're extracting, not adding - **Alternative is worse:** Each module implementing own logic = 3× the code - **Better testability:** 443 lines of tests once vs. duplicating tests for each module - **Standards-based:** Retry-After is RFC 7231, not custom logic ## Future Benefits **Weather migration (future PR):** Moving Weather from client-side to server-side will enable: - **Same robust error handling** - Weather gets 429 rate-limiting, 5xx backoff for free - **Simpler architecture** - No proxy layer needed Moving the weather modules from client-side to server-side will be a big undertaking, but I think it's a good strategy. Even if we only move the calendar and newsfeed to the new HTTP fetcher and leave the weather as it is, this PR still makes sense, I think. ## Breaking Changes **None** ---- I am eager to hear your opinion on this :slightly_smiling_face:
2026-01-22 19:24:37 +01:00
},
"#http_fetcher": {
"default": "./js/http_fetcher.js"
refactor default modules: move scheduleTimer to one place (#3837) see #3819 --------- Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com> Co-authored-by: Veeck <github@veeck.de>
2025-07-10 08:12:09 +02:00
}
},
Add pretty-quick
2020-05-11 21:59:45 +02:00
"main": "js/electron.js",
chore: update dependencies + add exports, files, and sideEffects fields to package.json (#4040) This updates all dependencies to their latest versions - except two packages: - eslint: Some plugins we use here aren't compatible yet to ESLint v10. - node-ical: The new version has revealed an issue in our calendar logic. I would prefer to address this in a separate PR. After updating the dependencies, eslint-plugin-package-json rules complained about missing fields in the package.json. I added them in the second commit.
2026-03-01 08:30:24 +01:00
"exports": "./js/electron.js",
"files": [
"clientonly",
"css",
"defaultmodules",
"js",
"serveronly",
"translations",
"favicon.svg",
"index.html"
],
"sideEffects": true,
Add pretty-quick
2020-05-11 21:59:45 +02:00
"scripts": {
Reactivate eslint-plugin-package-json (#3643) Somehow the plugin get lost when we moved to ESLint flat config. Now I reactivated it. One rules caused sorting the scripts. If this is not okay, I can undo this and switch off the rule. Thank's @bugsounet for the pinging in https://github.com/MagicMirrorOrg/MagicMirror/pull/3637#issuecomment-2509771362.
2024-12-01 15:26:23 +01:00
"config:check": "node js/check_config.js",
"install-mm": "npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev",
[core] refactor: replace `XMLHttpRequest` with `fetch` and migrate e2e tests to Playwright (#3950) ### 1. Replace `XMLHttpRequest` with the modern `fetch` API for loading translation files #### Changes - **translator.js**: Use `fetch` with `async/await` instead of XHR callbacks - **loader.js**: Align URL handling and add error handling (follow-up to fetch migration) - **Tests**: Update infrastructure for `fetch` compatibility #### Benefits - Modern standard API - Cleaner, more readable code - Better error handling and fallback mechanisms ### 2. Migrate e2e tests to Playwright This wasn't originally planned for this PR, but is related. While investigating suspicious log entries which surfaced after the fetch migration I kept running into JSDOM’s limitations. That pushed me to migrate the E2E suite to Playwright instead. #### Changes - switch e2e harness to Playwright (`tests/e2e/helpers/global-setup.js`) - rewrite specs to use Playwright locators + shared `expectTextContent` - install Chromium via `npx playwright install --with-deps` in CI #### Benefits - much closer to real browser behaviour - and no more fighting JSDOM’s quirks
2025-11-08 21:59:05 +01:00
"install-mm:dev": "npm install --no-audit --no-fund --no-update-notifier && npx playwright install chromium",
move custom.css from css to config (#4020) This is another change to cleanup structure, already mentioned in https://github.com/MagicMirrorOrg/MagicMirror/pull/4019#issuecomment-3792953018 After separating default and 3rd-party modules this PR moves the `custom.css` from the mm-owned directory `css` into user owned directory `config`. It has a built-in function which moves the `css/custom.css` to the new location `config/custom.css` (if the target not exists). Let me know if there's a majority in favor of this change.
2026-01-28 10:50:25 +01:00
"lint:css": "stylelint 'css/**/*.css' 'defaultmodules/**/*.css' --fix",
Update ESLint and simplify config (#3724) This does not change the rules of ESLint. It's just a little cosmetic fine-tuning.
2025-02-22 19:12:01 +01:00
"lint:js": "eslint --fix",
Add linting for markdown files (#3646) I also reworked the Linters section in `CONTRIBUTING.md` a bit and switched the `prettier` config to a flat config. Co-authored-by: Veeck <github@veeck.de>
2024-12-07 10:12:28 +01:00
"lint:markdown": "markdownlint-cli2 . --fix",
Reactivate eslint-plugin-package-json (#3643) Somehow the plugin get lost when we moved to ESLint flat config. Now I reactivated it. One rules caused sorting the scripts. If this is not okay, I can undo this and switch off the rule. Thank's @bugsounet for the pinging in https://github.com/MagicMirrorOrg/MagicMirror/pull/3637#issuecomment-2509771362.
2024-12-01 15:26:23 +01:00
"lint:prettier": "prettier . --write",
"prepare": "[ -f node_modules/.bin/husky ] && husky || echo no husky installed.",
"server": "node ./serveronly",
feat(core): add `server:watch` script with automatic restart on file changes (#3920) ## Description This PR adds a new `server:watch` script that runs MagicMirror² in server-only mode with automatic restart and browser reload capabilities. Particularly helpful for: - **Developers** who need to see changes immediately without manual restarts. - **Users setting up their mirror** who make many changes to `config.js` or `custom.css` and need quick feedback. ### What it does When you run `npm run server:watch`, the watcher monitors files you specify in `config.watchTargets`. Whenever a monitored file changes: 1. The server automatically restarts 2. Waits for the port to become available 3. Sends a reload notification to all connected browsers via Socket.io 4. Browsers automatically refresh to show the changes This creates a seamless development experience where you can edit code, save, and see the results within seconds. ### Implementation highlights **Zero dependencies:** Uses only Node.js built-ins (`fs.watch`, `child_process.spawn`, `net`, `http`) - no nodemon or external watchers needed. **Smart file watching:** Monitors parent directories instead of files directly to handle atomic writes from modern editors (VSCode, etc.) that create temporary files during save operations. **Port management:** Waits for the old server instance to fully release the port before starting a new one, preventing "port already in use" errors. ### Configuration Users explicitly define which files to monitor in their `config.js`: ```js let config = { watchTargets: [ "config/config.js", "css/custom.css", "modules/MMM-MyModule/MMM-MyModule.js", "modules/MMM-MyModule/node_helper.js" ], // ... rest of config }; ``` This explicit approach keeps the implementation simple (~260 lines) while giving users full control over what triggers restarts. If `watchTargets` is empty or undefined, the watcher starts but monitors nothing, logging a clear warning message. --- **Note:** This PR description has been updated to reflect the final implementation. During the review process, we refined the approach multiple times based on feedback. --------- Co-authored-by: Jboucly <contact@jboucly.fr> Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com>
2025-10-28 19:14:51 +01:00
"server:watch": "node ./serveronly/watcher.js",
Change default start scripts from X11 to Wayland (#4011) This PR changes the default `start` and `start:dev` scripts to use Wayland instead of X11. I think after three years, it's time to take this step. ### Background Since Raspberry Pi OS Bookworm (2023), Wayland is the default display server. As most MagicMirror installations run on Raspberry Pi, this change aligns with what new users already have installed. ### Benefits Especially for new users (which install the OS with Wayland) it's easier - they can simply run `npm start` without needing to understand display server differences or manually switch scripts. And for projects in general it's better to rely on modern defaults than on legacy. ### Breaking Changes **None** - X11 support is maintained. Users who really use and need X11 can use `node --run start:x11`.
2026-01-11 00:01:55 +01:00
"start": "node --run start:wayland",
"start:dev": "node --run start:wayland -- dev",
[core] fix: restore `--ozone-platform=wayland` flag for reliable Wayland support (#3989) The Electron 38+ auto-detection of ozone-platform does not work reliably in all environments (e.g., Docker containers) because it depends on environment variables like XDG_SESSION_TYPE which may not be set. Since `start:wayland` is explicitly called for Wayland sessions, it makes sense to explicitly specify the platform flag for maximum reliability. The `--enable-features=UseOzonePlatform` flag remains removed as it is no longer needed since Electron 38. Fixes Docker compatibility issue reported in MagicMirrorOrg/MagicMirror#3974
2025-12-14 19:45:20 +01:00
"start:wayland": "WAYLAND_DISPLAY=\"${WAYLAND_DISPLAY:=wayland-1}\" ./node_modules/.bin/electron js/electron.js --ozone-platform=wayland",
Use "node --run" instead of "npm run" (#3764) This has the advantage that the package manager is no longer involved after the installation process. However, previous start commands such as `npm run start` continue to work. So we don't even have to adapt the documentation.
2025-05-06 20:33:42 +02:00
"start:wayland:dev": "node --run start:wayland -- dev",
Add wayland and windows start options (#3594) This PR adds start options for Wayland and Windows. This would solve issue #3582. **To Do if this PR is merged:** - [ ] Adjust [Windows section](https://docs.magicmirror.builders/getting-started/installation.html#windows) in documentation - [ ] Add Wayland section to the documentation
2024-10-23 21:42:29 +02:00
"start:windows": ".\\node_modules\\.bin\\electron js\\electron.js",
Use "node --run" instead of "npm run" (#3764) This has the advantage that the package manager is no longer involved after the installation process. However, previous start commands such as `npm run start` continue to work. So we don't even have to adapt the documentation.
2025-05-06 20:33:42 +02:00
"start:windows:dev": "node --run start:windows -- dev",
Add wayland and windows start options (#3594) This PR adds start options for Wayland and Windows. This would solve issue #3582. **To Do if this PR is merged:** - [ ] Adjust [Windows section](https://docs.magicmirror.builders/getting-started/installation.html#windows) in documentation - [ ] Add Wayland section to the documentation
2024-10-23 21:42:29 +02:00
"start:x11": "DISPLAY=\"${DISPLAY:=:0}\" ./node_modules/.bin/electron js/electron.js",
Use "node --run" instead of "npm run" (#3764) This has the advantage that the package manager is no longer involved after the installation process. However, previous start commands such as `npm run start` continue to work. So we don't even have to adapt the documentation.
2025-05-06 20:33:42 +02:00
"start:x11:dev": "node --run start:x11 -- dev",
[tests] migrate from `jest` to `vitest` (#3940) This is a big change, but I think it's a good move, as `vitest` is much more modern than `jest`. I'm excited about the UI watch feature (run `npm run test:ui`), for example - it's really helpful and saves time when debugging tests. I had to adjust a few tests because they had time related issues, but basically we are now testing the same things - even a bit better and less flaky (I hope). What do you think?
2025-11-03 19:47:01 +01:00
"test": "vitest run",
move default modules from /modules/default to /defaultmodules (#4019) Since the project's inception, I've missed a clear separation between default and third-party modules. This increases complexity within the project (exclude `modules`, but not `modules/default`), but the mixed use is particularly problematic in Docker setups. Therefore, with this pull request, I'm moving the default modules to a different directory. ~~I've chosen `default/modules`, but I'm not bothered about it; `defaultmodules` or something similar would work just as well.~~ Changed to `defaultmodules`. Let me know if there's a majority in favor of this change.
2026-01-27 08:37:52 +01:00
"test:calendar": "node ./defaultmodules/calendar/debug.js",
[tests] migrate from `jest` to `vitest` (#3940) This is a big change, but I think it's a good move, as `vitest` is much more modern than `jest`. I'm excited about the UI watch feature (run `npm run test:ui`), for example - it's really helpful and saves time when debugging tests. I had to adjust a few tests because they had time related issues, but basically we are now testing the same things - even a bit better and less flaky (I hope). What do you think?
2025-11-03 19:47:01 +01:00
"test:coverage": "vitest run --coverage",
move custom.css from css to config (#4020) This is another change to cleanup structure, already mentioned in https://github.com/MagicMirrorOrg/MagicMirror/pull/4019#issuecomment-3792953018 After separating default and 3rd-party modules this PR moves the `custom.css` from the mm-owned directory `css` into user owned directory `config`. It has a built-in function which moves the `css/custom.css` to the new location `config/custom.css` (if the target not exists). Let me know if there's a majority in favor of this change.
2026-01-28 10:50:25 +01:00
"test:css": "stylelint 'css/**/*.css' 'defaultmodules/**/*.css'",
[tests] migrate from `jest` to `vitest` (#3940) This is a big change, but I think it's a good move, as `vitest` is much more modern than `jest`. I'm excited about the UI watch feature (run `npm run test:ui`), for example - it's really helpful and saves time when debugging tests. I had to adjust a few tests because they had time related issues, but basically we are now testing the same things - even a bit better and less flaky (I hope). What do you think?
2025-11-03 19:47:01 +01:00
"test:e2e": "vitest run tests/e2e",
"test:electron": "vitest run tests/electron",
Update ESLint and simplify config (#3724) This does not change the rules of ESLint. It's just a little cosmetic fine-tuning.
2025-02-22 19:12:01 +01:00
"test:js": "eslint",
Add linting for markdown files (#3646) I also reworked the Linters section in `CONTRIBUTING.md` a bit and switched the `prettier` config to a flat config. Co-authored-by: Veeck <github@veeck.de>
2024-12-07 10:12:28 +01:00
"test:markdown": "markdownlint-cli2 .",
Reactivate eslint-plugin-package-json (#3643) Somehow the plugin get lost when we moved to ESLint flat config. Now I reactivated it. One rules caused sorting the scripts. If this is not okay, I can undo this and switch off the rule. Thank's @bugsounet for the pinging in https://github.com/MagicMirrorOrg/MagicMirror/pull/3637#issuecomment-2509771362.
2024-12-01 15:26:23 +01:00
"test:prettier": "prettier . --check",
Add spell check (#3544) I felt like adding a spell checker, but it's okay if you find it superfluous. At least then we could fix the found spell issues. What is still missing is an automatic integration so that the spell checker does not have to be called manually. Would it perhaps make sense to always do it before a release?
2024-09-18 07:37:09 +02:00
"test:spelling": "cspell . --gitignore",
[tests] migrate from `jest` to `vitest` (#3940) This is a big change, but I think it's a good move, as `vitest` is much more modern than `jest`. I'm excited about the UI watch feature (run `npm run test:ui`), for example - it's really helpful and saves time when debugging tests. I had to adjust a few tests because they had time related issues, but basically we are now testing the same things - even a bit better and less flaky (I hope). What do you think?
2025-11-03 19:47:01 +01:00
"test:ui": "vitest --ui",
"test:unit": "vitest run tests/unit",
"test:watch": "vitest"
Add pretty-quick
2020-05-11 21:59:45 +02:00
},
Update deps (#3439) - update dependencies including electron to v30 - replace node v21 with v22 in tests
2024-05-01 19:54:38 +02:00
"lint-staged": {
chore: use `prettier --write --ignore-unknown` in `lint-staged` to avoid errors on unsupported files (#3888) This prevents `prettier` from failing when `lint-staged` passes unknown/binary files, making the pre-commit hook more robust. In concrete terms this could happen, when we, for example, add a new PNG file. Since we rarely do this, it has not been noticed so far. This is recommended when using asterisk: https://github.com/lint-staged/lint-staged#automatically-fix-code-style-with-prettier-for-any-format-prettier-supports ## before ```bash $ npx lint-staged <-- after staging a new PNG file ✔ Backed up original state in git stash (c3247d4b) ✔ Hiding unstaged changes to partially staged files... ⚠ Running tasks for staged files... ❯ package.json — 2 files ❯ * — 2 files ✖ prettier --write [FAILED] ↓ *.js — no files ↓ *.css — no files ↓ Skipped because of errors from tasks. ↓ Skipped because of errors from tasks. ✔ Reverting to original state because of errors... ✔ Cleaning up temporary files... ✖ prettier --write: [error] No parser could be inferred for file "~/MagicMirror/test.png". ... ``` ## after ```bash $ npx lint-staged <-- after staging a new PNG file ✔ Backed up original state in git stash (0c3fe285) ✔ Running tasks for staged files... ✔ Applying modifications from tasks... ✔ Cleaning up temporary files... ```
2025-09-11 18:34:08 +02:00
"*": "prettier --ignore-unknown --write",
Update deps (#3439) - update dependencies including electron to v30 - replace node v21 with v22 in tests
2024-05-01 19:54:38 +02:00
"*.js": "eslint --fix",
"*.css": "stylelint --fix"
Add pretty-quick
2020-05-11 21:59:45 +02:00
},
"dependencies": {
chore: update dependencies + add exports, files, and sideEffects fields to package.json (#4040) This updates all dependencies to their latest versions - except two packages: - eslint: Some plugins we use here aren't compatible yet to ESLint v10. - node-ical: The new version has revealed an issue in our calendar logic. I would prefer to address this in a separate PR. After updating the dependencies, eslint-plugin-package-json rules complained about missing fields in the package.json. I added them in the second commit.
2026-03-01 08:30:24 +01:00
"@fontsource/roboto": "^5.2.10",
update jsdoc and other deps (#3896) other cosmetic code changes because of new `eslint-plugin-jsdoc` version v60
2025-09-23 06:27:29 +02:00
"@fontsource/roboto-condensed": "^5.2.8",
chore: update dependencies + add exports, files, and sideEffects fields to package.json (#4040) This updates all dependencies to their latest versions - except two packages: - eslint: Some plugins we use here aren't compatible yet to ESLint v10. - node-ical: The new version has revealed an issue in our calendar logic. I would prefer to address this in a separate PR. After updating the dependencies, eslint-plugin-package-json rules complained about missing fields in the package.json. I added them in the second commit.
2026-03-01 08:30:24 +01:00
"@fortawesome/fontawesome-free": "^7.2.0",
simplify install and maintaining dependencies (#3795) I was always unhappy when maintaining dependency updates to have 3 `package.json` files. This PR moves all deps into the main `package.json` and removes the folders `fonts` and `vendor`. If accepted I will update the docs too. --------- Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com>
2025-06-01 17:03:11 +02:00
"animate.css": "^4.1.1",
chore: update dependencies + add exports, files, and sideEffects fields to package.json (#4040) This updates all dependencies to their latest versions - except two packages: - eslint: Some plugins we use here aren't compatible yet to ESLint v10. - node-ical: The new version has revealed an issue in our calendar logic. I would prefer to address this in a separate PR. After updating the dependencies, eslint-plugin-package-json rules complained about missing fields in the package.json. I added them in the second commit.
2026-03-01 08:30:24 +01:00
"croner": "^10.0.1",
update dependencies and workflows to node v26 (#4140)
2026-05-06 09:15:42 +02:00
"eslint": "^10.3.0",
[chore] update dependencies and min. node version (#3986)
2025-12-10 19:42:20 +01:00
"express": "^5.2.1",
Update dependencies incl ini
2020-12-11 11:09:52 +01:00
"feedme": "^2.0.2",
update dependencies and workflows to node v26 (#4140)
2026-05-06 09:15:42 +02:00
"globals": "^17.6.0",
update required node version and dependencies (#3747) see discussion in https://github.com/MagicMirrorOrg/MagicMirror/pull/3746 As [electron v35 requires node js v22.14.0](https://www.electronjs.org/blog/electron-35-0) we should update this here too.
2025-03-21 12:30:08 +01:00
"helmet": "^8.1.0",
update dependencies and workflows to node v26 (#4140)
2026-05-06 09:15:42 +02:00
"html-to-text": "^10.0.0",
update electron to v40, update node versions in workflows (#4018) - remove param `--enable-features=UseOzonePlatform` in start electron tests (as we did already in `package.json`) - update node versions in github workflows, remove `22.21.1`, add `25.x` - fix formatting in tests - update dependencies including electron to v40 This is still a draft PR because most calendar electron tests are not running which is caused by the electron update from `v39.3.0` to `v40.0.0`. Maybe @KristjanESPERANTO has an idea ... --------- Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com>
2026-01-24 13:15:15 +01:00
"iconv-lite": "^0.7.2",
update dependencies and workflows to node v26 (#4140)
2026-05-06 09:15:42 +02:00
"ipaddr.js": "^2.4.0",
Release 2.26.0 (#3319) ## [2.26.0] - 01-01-2024 Thanks to: @bnitkin, @bugsounet, @dependabot, @jkriegshauser, @kaennchenstruggle, @KristjanESPERANTO and @Ybbet. Special thanks to @khassel, @rejas and @sdetweil for taking over most (if not all) of the work on this release as project collaborators. This version would not be there without their effort. Thank you guys! You are awesome! This release also marks the latest release by Michael Teeuw. For more info, please read the following post: [A New Chapter for MagicMirror: The Community Takes the Lead](https://forum.magicmirror.builders/topic/18329/a-new-chapter-for-magicmirror-the-community-takes-the-lead). ### Added - Added update notification updater (for 3rd party modules) - Added node 21 to the test matrix - Added transform object to calendar:customEvents - Added ESLint rules for jest (including jest/expect-expect and jest/no-done-callback) ### Removed - Removed Codecov workflow (not working anymore, other workflow required) (#3107) - Removed titleReplace from calendar, replaced + extended by customEvents (backward compatibility included) (#3249) - Removed failing unit test (#3254) - Removed some unused variables ### Updated - Update electron to v27 and update other dependencies as well as github actions - Update newsfeed: Use `html-to-text` instead of regex for transform description - Review ESLint config (#3269) - Updated dependencies - Clock module: optionally display current moon phase in addition to rise/set times - electron is now per default started without gpu, if needed it must be enabled with new env var `ELECTRON_ENABLE_GPU=1` on startup (#3226) - Replace prettier by stylistic in ESLint config to lint JavaScript (and disable some rules for `config/config.js*` files) - Update node-ical to v0.17.1 and fix tests ### Fixed - Avoid fade out/in on updateDom when many calendars are used - Fix the option eventClass on customEvents. - Fix yr API version in locationforecast and sunrise call (#3227) - Fix cloneObject() function to respect RegExp (#3237) - Fix newsfeed module for feeds using "a10:updated" tag (#3238) - Fix issue template (#3167) - Fix #3256 filter out bad results from rrule.between - Fix calendar events sometimes not respecting deleted events (#3250) - Fix electron loadurl locally on Windows when address "0.0.0.0" (#2550) - Fix updatanotification (update_helper.js): catch error if reponse is not an JSON format (check PM2) - Fix missing typeof in calendar module - Fix style issues after prettier update - Fix calendar test (#3291) by moving "Exdate check" from e2e to electron to run on a Thursday - Fix calendar config params `fetchInterval` and `excludedEvents` were never used from single calendar config (#3297) - Fix MM_PORT variable not used in electron and allow full path for MM_CONFIG_FILE variable (#3302) --------- Signed-off-by: naveen <172697+naveensrinivasan@users.noreply.github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Karsten Hassel <hassel@gmx.de> Co-authored-by: Malte Hallström <46646495+SkySails@users.noreply.github.com> Co-authored-by: Veeck <github@veeck.de> Co-authored-by: veeck <michael@veeck.de> Co-authored-by: dWoolridge <dwoolridge@charter.net> Co-authored-by: Johan <jojjepersson@yahoo.se> Co-authored-by: Dario Mratovich <dario_mratovich@hotmail.com> Co-authored-by: Dario Mratovich <dario.mratovich@outlook.com> Co-authored-by: Magnus <34011212+MagMar94@users.noreply.github.com> Co-authored-by: Naveen <172697+naveensrinivasan@users.noreply.github.com> Co-authored-by: buxxi <buxxi@omfilm.net> Co-authored-by: Thomas Hirschberger <47733292+Tom-Hirschberger@users.noreply.github.com> Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com> Co-authored-by: Andrés Vanegas Jiménez <142350+angeldeejay@users.noreply.github.com> Co-authored-by: Dave Child <dave@addedbytes.com> Co-authored-by: grenagit <46225780+grenagit@users.noreply.github.com> Co-authored-by: Grena <grena@grenabox.fr> Co-authored-by: Magnus Marthinsen <magmar@online.no> Co-authored-by: Patrick <psieg@users.noreply.github.com> Co-authored-by: Piotr Rajnisz <56397164+rajniszp@users.noreply.github.com> Co-authored-by: Suthep Yonphimai <tomzt@users.noreply.github.com> Co-authored-by: CarJem Generations (Carter Wallace) <cwallacecs@gmail.com> Co-authored-by: Nicholas Fogal <nfogal.misc@gmail.com> Co-authored-by: JakeBinney <126349119+JakeBinney@users.noreply.github.com> Co-authored-by: OWL4C <124401812+OWL4C@users.noreply.github.com> Co-authored-by: Oscar Björkman <17575446+oscarb@users.noreply.github.com> Co-authored-by: Ismar Slomic <ismar@slomic.no> Co-authored-by: Jørgen Veum-Wahlberg <jorgen.wahlberg@amedia.no> Co-authored-by: Eddie Hung <6740044+eddiehung@users.noreply.github.com> Co-authored-by: Bugsounet - Cédric <github@bugsounet.fr> Co-authored-by: bugsounet <bugsounet@bugsounet.fr> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Knapoc <Knapoc@users.noreply.github.com> Co-authored-by: sam detweiler <sdetweil@gmail.com> Co-authored-by: veeck <michael.veeck@nebenan.de> Co-authored-by: Paranoid93 <6515818+Paranoid93@users.noreply.github.com> Co-authored-by: NolanKingdon <27908974+NolanKingdon@users.noreply.github.com> Co-authored-by: J. Kenzal Hunter <kenzal.hunter@gmail.com> Co-authored-by: Teddy <teddy.payet@gmail.com> Co-authored-by: TeddyStarinvest <teddy.payet@starinvest.com> Co-authored-by: martingron <61826403+martingron@users.noreply.github.com> Co-authored-by: dgoth <132394363+dgoth@users.noreply.github.com> Co-authored-by: kaennchenstruggle <54073894+kaennchenstruggle@users.noreply.github.com> Co-authored-by: jkriegshauser <jkriegshauser@gmail.com> Co-authored-by: Ben Nitkin <ben@nitkin.net>
2024-01-01 15:38:08 +01:00
"moment": "^2.30.1",
update dependencies (#4124)
2026-04-29 06:32:24 +02:00
"moment-timezone": "^0.6.2",
update dependencies and workflows to node v26 (#4140)
2026-05-06 09:15:42 +02:00
"node-ical": "^0.26.1",
simplify install and maintaining dependencies (#3795) I was always unhappy when maintaining dependency updates to have 3 `package.json` files. This PR moves all deps into the main `package.json` and removes the folders `fonts` and `vendor`. If accepted I will update the docs too. --------- Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com>
2025-06-01 17:03:11 +02:00
"nunjucks": "^3.2.4",
dependency update + adjust Playwright setup + fix linter issue (#3994) update dependencies before next release --------- Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com>
2025-12-28 12:14:31 +01:00
"socket.io": "^4.8.3",
move suncalc dependency out of dev, as it is used by the clock module (#3401) user reported problem with clock module, checking code found dependency on suncalc library, but it is not loaded in production mode.. move dependency --------- Co-authored-by: veeck <michael.veeck@nebenan.de>
2024-03-22 11:49:40 -07:00
"suncalc": "^1.9.0",
update dependencies (#4068) last update before release
2026-03-31 23:59:10 +02:00
"systeminformation": "^5.31.5",
update dependencies and workflows to node v26 (#4140)
2026-05-06 09:15:42 +02:00
"undici": "^8.2.0",
simplify install and maintaining dependencies (#3795) I was always unhappy when maintaining dependency updates to have 3 `package.json` files. This PR moves all deps into the main `package.json` and removes the folders `fonts` and `vendor`. If accepted I will update the docs too. --------- Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com>
2025-06-01 17:03:11 +02:00
"weathericons": "^2.1.0"
Release v2.25.0 (#3214) ## [2.25.0] - 2023-10-01 Thanks to: @bugsounet, @dgoth, @dependabot, @kenzal, @Knapoc, @KristjanESPERANTO, @martingron, @NolanKingdon, @Paranoid93, @TeddyStarinvest and @Ybbet. Special thanks to @khassel, @rejas and @sdetweil for taking over most (if not all) of the work on this release as project collaborators. This version would not be there without their effort. Thank you guys! You are awesome! > ⚠️ This release needs nodejs version >= `v18`, older releases have reached end of life and will not work! ### Added - Added UV Index support to OpenWeatherMap - Added 'hideDuplicates' flag to the calendar module - Added `allowOverrideNotification` to weather module to enable sending current weather objects with the `CURRENT_WEATHER_OVERRIDE` notification to supplement/replace the current weather displayed - Added optional AnimateCSS animate for `hide()`, `show()`, `updateDom()` - Added AnimateIn and animateOut in module config definition - Apply AnimateIn rules on the first start - Added automatic client page reload when server was restarted by setting `reloadAfterServerRestart: true` in `config.js`, per default `false` (#3105) - Added eventClass option for customEvents on the default calendar - Added AnimateCSS integration in tests suite (#3206) - Added npm dependabot [Reserved to developer] (#3210) - Added improved logging for calendar (#3110) ### Removed - **Breaking Change**: Removed `digest` authentication method from calendar module (which was already broken since release `2.15.0`) ### Updated - Update roboto fonts to version v5 - Update issue template - Update dev/dependencies incl. electron to v26 - Replace pretty-quick by lint-staged (<https://github.com/azz/pretty-quick/issues/164>) - Update engine node >=18. v16 reached it's end of life. (#3170) - Update typescript definition for modules - Cleaned up nunjuck templates - Replace `node-fetch` with internal fetch (#2649) and remove `digest-fetch` - Update the French translation according to the English file. - Update dependabot incl. vendor/fonts (monthly check) - Renew `package-lock.json` for release ### Fixed - Fix engine check on npm install (#3135) - Fix undefined formatTime method in clock module (#3143) - Fix clientonly startup fails after async added (#3151) - Fix electron width/heigth when using xrandr under bullseye - Fix time issue with certain recurring events in calendar module - Fix ipWhiteList test (#3179) - Fix newsfeed: Convert HTML entities, codes and tag in description (#3191) - Respect width/height (no fullscreen) if set in electronOptions (together with `fullscreen: false`) in `config.js` (#3174) - Fix: AnimateCSS merge hide() and show() animated css class when we do multiple call - Fix `Uncaught SyntaxError: Identifier 'getCorsUrl' has already been declared (at utils.js:1:1)` when using `clock` and `weather` module (#3204) - Fix overriding `config.js` when running tests (#3201) - Fix issue in weathergov provider with probability of precipitation not showing up on hourly or daily forecast --------- Signed-off-by: naveen <172697+naveensrinivasan@users.noreply.github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Karsten Hassel <hassel@gmx.de> Co-authored-by: Malte Hallström <46646495+SkySails@users.noreply.github.com> Co-authored-by: Veeck <github@veeck.de> Co-authored-by: veeck <michael@veeck.de> Co-authored-by: dWoolridge <dwoolridge@charter.net> Co-authored-by: Johan <jojjepersson@yahoo.se> Co-authored-by: Dario Mratovich <dario_mratovich@hotmail.com> Co-authored-by: Dario Mratovich <dario.mratovich@outlook.com> Co-authored-by: Magnus <34011212+MagMar94@users.noreply.github.com> Co-authored-by: Naveen <172697+naveensrinivasan@users.noreply.github.com> Co-authored-by: buxxi <buxxi@omfilm.net> Co-authored-by: Thomas Hirschberger <47733292+Tom-Hirschberger@users.noreply.github.com> Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com> Co-authored-by: Andrés Vanegas Jiménez <142350+angeldeejay@users.noreply.github.com> Co-authored-by: Dave Child <dave@addedbytes.com> Co-authored-by: grenagit <46225780+grenagit@users.noreply.github.com> Co-authored-by: Grena <grena@grenabox.fr> Co-authored-by: Magnus Marthinsen <magmar@online.no> Co-authored-by: Patrick <psieg@users.noreply.github.com> Co-authored-by: Piotr Rajnisz <56397164+rajniszp@users.noreply.github.com> Co-authored-by: Suthep Yonphimai <tomzt@users.noreply.github.com> Co-authored-by: CarJem Generations (Carter Wallace) <cwallacecs@gmail.com> Co-authored-by: Nicholas Fogal <nfogal.misc@gmail.com> Co-authored-by: JakeBinney <126349119+JakeBinney@users.noreply.github.com> Co-authored-by: OWL4C <124401812+OWL4C@users.noreply.github.com> Co-authored-by: Oscar Björkman <17575446+oscarb@users.noreply.github.com> Co-authored-by: Ismar Slomic <ismar@slomic.no> Co-authored-by: Jørgen Veum-Wahlberg <jorgen.wahlberg@amedia.no> Co-authored-by: Eddie Hung <6740044+eddiehung@users.noreply.github.com> Co-authored-by: Bugsounet - Cédric <github@bugsounet.fr> Co-authored-by: bugsounet <bugsounet@bugsounet.fr> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Knapoc <Knapoc@users.noreply.github.com> Co-authored-by: sam detweiler <sdetweil@gmail.com> Co-authored-by: veeck <michael.veeck@nebenan.de> Co-authored-by: Paranoid93 <6515818+Paranoid93@users.noreply.github.com> Co-authored-by: NolanKingdon <27908974+NolanKingdon@users.noreply.github.com> Co-authored-by: J. Kenzal Hunter <kenzal.hunter@gmail.com> Co-authored-by: Teddy <teddy.payet@gmail.com> Co-authored-by: TeddyStarinvest <teddy.payet@starinvest.com> Co-authored-by: martingron <61826403+martingron@users.noreply.github.com> Co-authored-by: dgoth <132394363+dgoth@users.noreply.github.com>
2023-10-01 20:13:41 +02:00
},
Update deps (#3439) - update dependencies including electron to v30 - replace node v21 with v22 in tests
2024-05-01 19:54:38 +02:00
"devDependencies": {
chore: upgrade ESLint to v10 and fix newly surfaced issues (#4057) `eslint-plugin-import-x` was the last thing blocking the ESLint v10 upgrade - it just got v10 support. So here we go. The upgrade itself is tiny. The rest of the diff is cleanup from issues ESLint v10 now catches: a few `let` declarations with initial values that were immediately overwritten anyway (`no-useless-assignment`), and `Translator` listed in `/* global */` in `main.js` and `module.js`. Working through those `no-useless-assignment` warnings also surfaced a dead default in `openmeteo`: `maxEntries: 5` in the constructor, which was never actually doing anything - `openmeteo` never reads `this.config.maxEntries` anywhere. And `weather.js` already sets that default for all providers, so it was just a redundant duplicate. Removed that too. No runtime behavior changes.
2026-03-12 11:58:26 +01:00
"@eslint/js": "^10.0.1",
chore: update ESLint and plugins, simplify config, apply new rules (#4052) This PR updates ESLint and the ESLint plugins to their latest versions and takes advantage of the new versions to simplify the config. The main cleanup: removed all explicit `plugins: {}` registrations from `eslint.config.mjs`. When passing direct config objects like `js.configs.recommended`, the plugin registration is already included – we were just doing it twice. Two lint warnings are also fixed: - A wrong import style for `eslint-plugin-package-json` (named vs. default) - `playwright/no-duplicate-hooks` is disabled for e2e tests – the rule doesn't handle plain `beforeAll()`/`afterAll()` (Vitest style) correctly and produces false positives. I've created an issue for that: https://github.com/mskelton/eslint-plugin-playwright/issues/443. Built-in Node.js imports were manually updated to use the `node:` prefix (e.g. `require("fs")` → `require("node:fs")`). Minor formatting fixes were applied automatically by `eslint --fix`.
2026-03-07 16:34:28 +01:00
"@stylistic/eslint-plugin": "^5.10.0",
update dependencies (#4124)
2026-04-29 06:32:24 +02:00
"@vitest/coverage-v8": "^4.1.5",
"@vitest/eslint-plugin": "^1.6.16",
"@vitest/ui": "^4.1.5",
"cspell": "^10.0.0",
chore: upgrade ESLint to v10 and fix newly surfaced issues (#4057) `eslint-plugin-import-x` was the last thing blocking the ESLint v10 upgrade - it just got v10 support. So here we go. The upgrade itself is tiny. The rest of the diff is cleanup from issues ESLint v10 now catches: a few `let` declarations with initial values that were immediately overwritten anyway (`no-useless-assignment`), and `Translator` listed in `/* global */` in `main.js` and `module.js`. Working through those `no-useless-assignment` warnings also surfaced a dead default in `openmeteo`: `maxEntries: 5` in the constructor, which was never actually doing anything - `openmeteo` never reads `this.config.maxEntries` anywhere. And `weather.js` already sets that default for all providers, so it was just a redundant duplicate. Removed that too. No runtime behavior changes.
2026-03-12 11:58:26 +01:00
"eslint-plugin-import-x": "^4.16.2",
chore: update dependencies (#4088) `node-ical` has released a new version that fixes an issue reported by one of our users (https://github.com/jens-maus/node-ical/issues/495). I'd like to have that in the develop branch. Instead of just updating that, I think it would make sense to include the others as well. `undici` had a major release but according to the release notes we are not affected.
2026-04-04 15:01:27 +02:00
"eslint-plugin-jsdoc": "^62.9.0",
update dependencies (#4124)
2026-04-29 06:32:24 +02:00
"eslint-plugin-package-json": "^0.91.2",
"eslint-plugin-playwright": "^2.10.2",
Update deps (#3439) - update dependencies including electron to v30 - replace node v21 with v22 in tests
2024-05-01 19:54:38 +02:00
"express-basic-auth": "^1.2.1",
update dependencies (#3657)
2024-12-18 22:04:16 +01:00
"husky": "^9.1.7",
update dependencies and workflows to node v26 (#4140)
2026-05-06 09:15:42 +02:00
"jsdom": "^29.1.1",
update eletron to v42 (#4144) additional things: - removed fix chrome-sandbox permissions (runs without) - added `npx install-electron` which downloads the electron binaries new in v42: > Electron now downloads its binary into node_modules dynamically on first launch instead of running a postinstall script. Added the install-electron script to manually trigger the download as well. https://github.com/electron/electron/pull/49328
2026-05-06 20:25:37 +02:00
"lint-staged": "^17.0.2",
update dependencies (#4124)
2026-04-29 06:32:24 +02:00
"markdownlint-cli2": "^0.22.1",
update dependencies and workflows to node v26 (#4140)
2026-05-06 09:15:42 +02:00
"msw": "^2.14.3",
chore: update dependencies (#4088) `node-ical` has released a new version that fixes an issue reported by one of our users (https://github.com/jens-maus/node-ical/issues/495). I'd like to have that in the develop branch. Instead of just updating that, I think it would make sense to include the others as well. `undici` had a major release but according to the release notes we are not affected.
2026-04-04 15:01:27 +02:00
"playwright": "^1.59.1",
update dependencies (#4124)
2026-04-29 06:32:24 +02:00
"prettier": "^3.8.3",
update dependencies and workflows to node v26 (#4140)
2026-05-06 09:15:42 +02:00
"prettier-plugin-jinja-template": "^2.2.0",
"stylelint": "^17.11.0",
update electron to v40, update node versions in workflows (#4018) - remove param `--enable-features=UseOzonePlatform` in start electron tests (as we did already in `package.json`) - update node versions in github workflows, remove `22.21.1`, add `25.x` - fix formatting in tests - update dependencies including electron to v40 This is still a draft PR because most calendar electron tests are not running which is caused by the electron update from `v39.3.0` to `v40.0.0`. Maybe @KristjanESPERANTO has an idea ... --------- Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com>
2026-01-24 13:15:15 +01:00
"stylelint-config-standard": "^40.0.0",
[tests] migrate from `jest` to `vitest` (#3940) This is a big change, but I think it's a good move, as `vitest` is much more modern than `jest`. I'm excited about the UI watch feature (run `npm run test:ui`), for example - it's really helpful and saves time when debugging tests. I had to adjust a few tests because they had time related issues, but basically we are now testing the same things - even a bit better and less flaky (I hope). What do you think?
2025-11-03 19:47:01 +01:00
"stylelint-prettier": "^5.0.3",
update dependencies (#4124)
2026-04-29 06:32:24 +02:00
"vitest": "^4.1.5"
Add pretty-quick
2020-05-11 21:59:45 +02:00
},
Update deps (#3439) - update dependencies including electron to v30 - replace node v21 with v22 in tests
2024-05-01 19:54:38 +02:00
"optionalDependencies": {
update eletron to v42 (#4144) additional things: - removed fix chrome-sandbox permissions (runs without) - added `npx install-electron` which downloads the electron binaries new in v42: > Electron now downloads its binary into node_modules dynamically on first launch instead of running a postinstall script. Added the install-electron script to manually trigger the download as well. https://github.com/electron/electron/pull/49328
2026-05-06 20:25:37 +02:00
"electron": "^42.0.0"
Add pretty-quick
2020-05-11 21:59:45 +02:00
},
Added engine fields into package json
2021-01-05 09:54:03 +01:00
"engines": {
[chore] update dependencies and min. node version (#3986)
2025-12-10 19:42:20 +01:00
"node": ">=22.21.1 <23 || >=24"
Add pretty-quick
2020-05-11 21:59:45 +02:00
}
Clean Up the Contributing Documentation and Process: Part II * Add `grunt-stylelint` over the complicated PostCSS method previously used. * Remove PostCSS dependencies.
2016-09-08 15:14:00 -04:00
}
Reference in New Issue Copy Permalink