Error when running npx create-local-addon

[josephfusco]

Here is the output I'm seeing after running npx create-local-addon and answering the initial prompts.

Using Node v18.16.0

Need to install the following packages:
  [email protected]
Ok to proceed? (y)
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
? May Local Add-on Creator anonymously report usage statistics to improve our tool over time? We will not collect any personal information about you or your add-on — only the way you use this tool. No

Hello! We are here today to create a new add-on for the Local application. Yay!
We are planning to pull down a basic add-on –– just a little something to act as a starting point for your add-on development.
Then we'll do some basic setup: put your files where you want them, make sure Local knows about your add-on, and get you up and running as soon as possible!
You can customize the setup a bit if you want! Run  create-local-addon --help  to learn more.

Okay, let's get started!
? What is the name of your addon? This will be shown to users. symlinked-plugin-development
? We would like to make a directory for your add-on. What would you like to name this directory? symlinked-plugin-development
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^8.50.0" from the root project
npm ERR!   peer eslint@">= 4.12.1" from [email protected]
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/[email protected]
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/[email protected]
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/joe.fusco/.npm/_logs/2023-10-13T14_35_09_035Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/joe.fusco/.npm/_logs/2023-10-13T14_35_09_035Z-debug-0.log

> [email protected] 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:
→  A symlink pointing to your add-on directory has been made in the Local add-ons directory:

        /Users/joe.fusco/Library/Application Support/Local/addons/symlinked-plugin-development

→  You can change your add-on by making changes to the source files:

        /Users/joe.fusco/Code/symlinked-plugin-development/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/joe.fusco/Code/symlinked-plugin-development
	 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 https://localwp.com/get-involved
→  Thinking of submiting your add-on to the Local add-on marketplace? Visit https://localwp.com/submit-addon
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.

[robruiz]

I'm getting the same thing. I'm running on Windows 11. Actually, I can't get the new add-on to run at all in Local on Windows 11.