search

qjebbs / vscode-markdown-extended

Extended syntaxes to built-in markdown & What you see is what you get exporter.
MIT License
125 stars 25 forks source link

Unable to export to file since 1.1.4 #161

Open piridium opened 6 months ago

piridium commented 6 months ago

Since 1.1.4 I am unable to export files. This is the error message I get:

ENOENT: no such file or directory, stat 'extension-output-jebbs.markdown-extended-#1-MDExtended'
Error: ENOENT: no such file or directory, stat 'extension-output-jebbs.markdown-extended-#1-MDExtended'
    at statSync (node:fs:1692:3)
    at node:electron/js2c/node_init:2:4795
    at Object.n.statSync (/Users/max/.vscode/extensions/esbenp.prettier-vscode-10.4.0/dist/extension.js:1:3435)
    at getFileList (/Users/max/.vscode/extensions/jebbs.markdown-extended-1.1.4/out/src/services/exporter/export.js:27:48)
    at MarkdownExport (/Users/max/.vscode/extensions/jebbs.markdown-extended-1.1.4/out/src/services/exporter/export.js:10:24)
    at /Users/max/.vscode/extensions/jebbs.markdown-extended-1.1.4/out/src/commands/exportUri.js:20:48
    at v.d (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:150:151992)
    at v.withProgress (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:150:151855)
    at Object.withProgress (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:160:32751)
    at exportUri (/Users/max/.vscode/extensions/jebbs.markdown-extended-1.1.4/out/src/commands/exportUri.js:17:26)

I already tried to set puppeteer executable to '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome' with no luck.

Could not find Chromium (rev. 1108766). This can occur if either
 1. you did not perform an installation before running the script (e.g. `npm install`) or
 2. your cache path is incorrectly configured (which is: /Users/max/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
Error: Could not find Chromium (rev. 1108766). This can occur if either
 1. you did not perform an installation before running the script (e.g. `npm install`) or
 2. your cache path is incorrectly configured (which is: /Users/max/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
    at ChromeLauncher.resolveExecutablePath (/Users/max/.vscode/extensions/jebbs.markdown-extended-1.1.4/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:289:27)
    at ChromeLauncher.executablePath (/Users/max/.vscode/extensions/jebbs.markdown-extended-1.1.4/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:182:25)
    at PuppeteerNode.executablePath (/Users/max/.vscode/extensions/jebbs.markdown-extended-1.1.4/node_modules/puppeteer-core/lib/cjs/puppeteer/node/PuppeteerNode.js:156:105)
    at PuppeteerExporter.checkPuppeteerBinary (/Users/max/.vscode/extensions/jebbs.markdown-extended-1.1.4/out/src/services/exporter/puppeteer.js:81:79)
    at PuppeteerExporter.Export (/Users/max/.vscode/extensions/jebbs.markdown-extended-1.1.4/out/src/services/exporter/puppeteer.js:17:19)
    at MarkdownExport (/Users/max/.vscode/extensions/jebbs.markdown-extended-1.1.4/out/src/services/exporter/export.js:16:28)

I ran npm install inside ~/.vscode/extensions/jebbs.markdown-extended-1.1.4 which did not help either. Rolling back to 1.1.3 everything works fine.

qjebbs commented 6 months ago

This is because your file to export is not saved, 1.1.3 should act the same way.

piridium commented 6 months ago

No, this is not the case. The file is properly saved and I can export it with 1.1.3 but not with 1.1.4. I also checked if there's any difference if I just open the file or open the containing folder as workspace. There is no difference in the behaviour.

qjebbs commented 6 months ago

I can't reproduce it on my side

0xD0M1M0 commented 6 months ago

Can confirm the issue

c4tom commented 5 months ago

I have the same problem when I try to export to PDF 

could not find Chromium (rev. 1108766). This can occur if either
 1. you did not perform an installation before running the script (e.g. `npm install`) or
 2. your cache path is incorrectly configured (which is: /home/can/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
Error: Could not find Chromium (rev. 1108766). This can occur if either
 1. you did not perform an installation before running the script (e.g. `npm install`) or
 2. your cache path is incorrectly configured (which is: /home/can/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
    at ChromeLauncher.resolveExecutablePath (/home/can/.vscode/extensions/jebbs.markdown-extended-1.1.4/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:289:27)
    at ChromeLauncher.executablePath (/home/can/.vscode/extensions/jebbs.markdown-extended-1.1.4/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:182:25)
    at PuppeteerNode.executablePath (/home/can/.vscode/extensions/jebbs.markdown-extended-1.1.4/node_modules/puppeteer-core/lib/cjs/puppeteer/node/PuppeteerNode.js:156:105)
    at PuppeteerExporter.checkPuppeteerBinary (/home/can/.vscode/extensions/jebbs.markdown-extended-1.1.4/out/src/services/exporter/puppeteer.js:81:79)
    at PuppeteerExporter.Export (/home/can/.vscode/extensions/jebbs.markdown-extended-1.1.4/out/src/services/exporter/puppeteer.js:17:19)
    at MarkdownExport (/home/can/.vscode/extensions/jebbs.markdown-extended-1.1.4/out/src/services/exporter/export.js:16:28)

cat /etc/os-release 
NAME="Linux Mint"
VERSION="21.3 (Virginia)"
ID=linuxmint
ID_LIKE="ubuntu debian"
PRETTY_NAME="Linux Mint 21.3"
VERSION_ID="21.3"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.linuxmint.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=virginia
UBUNTU_CODENAME=jammy
atheerix commented 5 months ago

I have the same problem too, with Win 11 Pro and Mac OS

Could not find Chromium (rev. 1108766). This can occur if either
 1. you did not perform an installation before running the script (e.g. `npm install`) or
 2. your cache path is incorrectly configured (which is: C:\Users\arix\.cache\puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
Error: Could not find Chromium (rev. 1108766). This can occur if either
 1. you did not perform an installation before running the script (e.g. `npm install`) or
 2. your cache path is incorrectly configured (which is: C:\Users\arix\.cache\puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
    at ChromeLauncher.resolveExecutablePath (c:\Users\arix\.vscode\extensions\jebbs.markdown-extended-1.1.4\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ProductLauncher.js:289:27)
    at ChromeLauncher.executablePath (c:\Users\arix\.vscode\extensions\jebbs.markdown-extended-1.1.4\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ChromeLauncher.js:182:25)
    at PuppeteerNode.executablePath (c:\Users\arix\.vscode\extensions\jebbs.markdown-extended-1.1.4\node_modules\puppeteer-core\lib\cjs\puppeteer\node\PuppeteerNode.js:156:105)
    at PuppeteerExporter.checkPuppeteerBinary (c:\Users\arix\.vscode\extensions\jebbs.markdown-extended-1.1.4\out\src\services\exporter\puppeteer.js:81:79)
    at PuppeteerExporter.Export (c:\Users\arix\.vscode\extensions\jebbs.markdown-extended-1.1.4\out\src\services\exporter\puppeteer.js:17:19)
    at MarkdownExport (c:\Users\arix\.vscode\extensions\jebbs.markdown-extended-1.1.4\out\src\services\exporter\export.js:16:28)
gbougeniere commented 4 months ago

Same problem here on a fresh windows install

Sweefiez commented 3 months ago

I had the same problem with version 1.1.4, but I switched to version 1.1.3 and it works fine for me. I'm running Windows 10

dominotec commented 3 months ago

I had the same problem with version 1.1.4 after vsCode update to version 1.19.0, but I switched to version 1.1.3 and it works. I'm running Windows 11.