What issue or error are you experiencing?
Hello, I am trying to create a new addon for local. However when following the steps here: GitHub - getflywheel/create-local-addon: A generator to assist in the development of new Local add-ons. Generates a basic add-on to act as a starting point for development. i get a series of errors and the addon is not showing up in local despite restarting it. Ive added the addon to the addons folder and it is still not showing up. I have been able to create a addon in the past but that was many versions of local ago
These are the errors I get when running the npx create-local-addon:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: seoplus-deploy-addon@1.0.0
npm ERR! Found: eslint@8.50.0
npm ERR! node_modules/eslint
npm ERR! dev eslint@“^8.50.0” from the root project
npm ERR! peer eslint@“>= 4.12.1” from babel-eslint@10.1.0
npm ERR! node_modules/babel-eslint
npm ERR! dev babel-eslint@“^10.1.0” from the root project
npm ERR! peer babel-eslint@“^10.0.1” from @getflywheel/eslint-config-local@1.0.4
npm ERR! node_modules/@getflywheel/eslint-config-local
npm ERR! dev @getflywheel/eslint-config-local@“1.0.4” from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@“^5.0.0” from @getflywheel/eslint-config-local@1.0.4
npm ERR! node_modules/@getflywheel/eslint-config-local
npm ERR! dev @getflywheel/eslint-config-local@“1.0.4” from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/alexfoster/.npm/_logs/2025-01-21T16_55_34_933Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /Users/alexfoster/.npm/_logs/2025-01-21T16_55_34_933Z-debug-0.log
seoplus-deploy-addon@1.0.0 build
tsc
sh: tsc: command not found
NEXT STEPS
If Local is already running, you will need to restart the application in order for your add-on to appear.
Making changes to your add-on:
→ You can change your add-on by making changes to the source files:
/Users/alexfoster/Library/Application Support/Local/addons/seoplus-deploy-addon/src
(Boilerplate.jsx and renderer.jsx will have some basic logic in them to give you a starting point, but you’ll probably want to make some changes.)
→ Compile, watch add-on source files, and trigger recompilation on change:
cd /Users/alexfoster/Library/Application Support/Local/addons/seoplus-deploy-addon
npm run build --watch
(You can leave the --watch flag off if you just want to compile your changes once.)
NEED SOME HELP?
→ Looking for resources to help you get started with your add-on? Visit Get Involved - Local
→ Thinking of submiting your add-on to the Local add-on marketplace? Visit Submit an Add-on - Local
Okay, we’ll get out of the way and let you start developing! If you have any questions or concerns, try consulting the documentation for Local add-on development.
What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc
npx create-local-addon --place-directly
System Details
- Local Version:
Version 9.2.0+6762 - Operating System (OS) and OS version:
MacOS Sonoma 14.6.1
Local Logs
Attach your Local Logs here (Help Doc - Retrieving Local’s Log)
Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.