-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error running via npx : "SyntaxError: Unexpected token ." #441
Comments
Yihaa, thank you for reporting me this issue and to let me improve Yarle! |
hi @noofny , pls try to use Yarle via UI until i fix this issue. Thanks for reporting it, i'll do my best to sort it out soon! |
Super quick response, wow thank you @akosbalasko - also thank you for your efforts on the tool. Once I see it will work for my use I'll help by donating. One question: when I use the GUI (as I have been doing) - is there a way to specify your own Anyways, thanks again for your efforts, your tool is the only decent tool around that does this conversion and provides great options. |
Hi @noofny About npx: could you please clear cache and try again on node 19 (it should work also,however it is tested on 14 16 and 18):
|
@noofny any news? |
My apologies @akosbalasko I was away over the weekend. Just tried now by clearing cache and re-running, sadly the same error appears... npm ERR! cb.apply is not a function
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/me/.npm/_logs/2023-01-30T00_43_01_988Z-debug.log
Install for [ 'yarle-evernote-to-md@latest' ] failed with code 1 Contents of that log file are...
Thanks for following up. When you select "LogSeq" as the target dialect, the GUI disables editing of the template text box (does not happen when selecting other dialect options), if this could not happen, so that you can still edit the template, it would solve half of my problem as I could at least change the behavior of the tags/output. Perhaps another idea is to have a button that the user can load/open a |
Got it working. It was nothing wrong with your code, just a local machine/environment issue. FWIW below are the 2 links that ended up guiding me out of the forest, but I ended up doing a full uninstall of Node and a manual cleanup, then a clean install using brew.
What I ended up with as a working environment was... $ node --version
v19.5.0
$ npm --version
9.3.1
$ npx --version
9.3.1 Thanks again for your support. |
This error appears when attempting to execute directly using
npx
as per the README...Also tried using the default config file bundled with latest code.
Running on macOS 12.6.2 (21G320)
Upgraded node/npm/npx, now raises the following error...
Log file from above
/Users/me/.npm/_logs/2023-01-25T04_34_30_599Z-debug.log
is as follows...The text was updated successfully, but these errors were encountered: