Closed steevech closed 6 years ago
Do you still have the problem? Have you reinstalled the package once?
When starting Atom 1.25.0-beta1, markdown-themeable-pdf was working at one point. Now I receive this, have tried reinstalling the module. I don't know much about the internals of Atom so haven't debugged. Any thoughts if this is related?
TypeError: Path must be a string. Received undefined
at assertPath (path.js:7:11)
at Object.resolve (path.js:1146:7)
at Object.activate (/Users/ronaldpetty/.atom/packages/markdown-themeable-pdf/lib/markdown-themeable-pdf.js:212:40)
at Package.activateNow (/Applications/Atom Beta.app/Contents/Resources/app/src/package.js:230:33)
at measure (/Applications/Atom Beta.app/Contents/Resources/app/src/package.js:206:33)
at Package.measure (/Applications/Atom Beta.app/Contents/Resources/app/src/package.js:88:25)
at activationPromise.Promise (/Applications/Atom Beta.app/Contents/Resources/app/src/package.js:200:20)
at Promise (<anonymous>)
at Package.activate (/Applications/Atom Beta.app/Contents/Resources/app/src/package.js:198:38)
at PackageManager.activatePackage (/Applications/Atom Beta.app/Contents/Resources/app/src/package-manager.js:695:42)
at config.transactAsync (/Applications/Atom Beta.app/Contents/Resources/app/src/package-manager.js:670:36)
at Config.transactAsync (/Applications/Atom Beta.app/Contents/Resources/app/src/config.js:852:28)
at PackageManager.activatePackages (/Applications/Atom Beta.app/Contents/Resources/app/src/package-manager.js:668:23)
at PackageManager.activate (/Applications/Atom Beta.app/Contents/Resources/app/src/package-manager.js:647:50)
at loadStatePromise.loadState.then (/Applications/Atom Beta.app/Contents/Resources/app/src/atom-environment.js:867:27)
at <anonymous>
I take it thats a no ;)
I'm currently doing a rewrite of the entire package. Unfortunately, I could not reproduce your problem. Maybe it will be fixed afterwards for you!
I can confirm this issue on 1.25.0-beta2, but as you say, rewrite might fix it.
Issue confirmed on 1.25.0
I got the same issues with 1.25.0 with macOS 10.11.6.
Path must be a string. Received undefined
TypeError: Path must be a string. Received undefined
at assertPath (path.js:7:11)
at Object.resolve (path.js:1146:7)
at Object.activate (/Users/Alex/.atom/packages/markdown-themeable-pdf/lib/markdown-themeable-pdf.js:212:40)
at Package.activateNow (/Applications/Atom.app/Contents/Resources/app/src/package.js:230:33)
at measure (/Applications/Atom.app/Contents/Resources/app/src/package.js:206:33)
at Package.measure (/Applications/Atom.app/Contents/Resources/app/src/package.js:88:25)
at activationPromise.Promise (/Applications/Atom.app/Contents/Resources/app/src/package.js:200:20)
at Promise (<anonymous>)
at Package.activate (/Applications/Atom.app/Contents/Resources/app/src/package.js:198:38)
at PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:695:42)
at /Applications/Atom.app/Contents/Resources/app/node_modules/settings-view/lib/package-manager.js:491:35
at exit (/Applications/Atom.app/Contents/Resources/app/node_modules/settings-view/lib/package-manager.js:128:22)
at triggerExitCallback (/Applications/Atom.app/Contents/Resources/app/src/buffered-process.js:267:15)
at bufferStream (/Applications/Atom.app/Contents/Resources/app/src/buffered-process.js:288:15)
at Socket.stream.on (/Applications/Atom.app/Contents/Resources/app/src/buffered-process.js:164:13)
at emitOne (events.js:101:20)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)
can confirm on 1.25.0
same problem in 1.2.0 with win10.
+1 1.25.0 on Fedora 27.
I had to do this manual change in 3 places (markdown-themeable-pdf.js, ..) and then it worked. The configDirPath is not set for some reason. I don't know enough on atom at moment to fix properly.
var global = path.join("/Users/ronaldpetty/.atom", relativePath);
//RON was here - var global = path.join(atom.config.configDirPath, relativePath);
In a couple of places.
the above worked for me on Windows
Currently I'm doing a complete rewrite. I have already noticed this while programming and corrected there. In the Specs it behaves differently and resolves (Arch Linux) to /tmp/
on. oO
Any Atom update has probably changed that.
I fix this for the v1 version before the v2 is released... #101
Thanks!
Appears fixed in v1.2.1, thank you!
No problem ;)
Thanks a lot.
[Enter steps to reproduce:]
I got the error: "ENOENT: no such file or directory, scandir '/Users/steevechwojko/.atom/packages/markdown-themeable-pdf-1.2.0/node_modules/highlight.js/styles'
I manually created this path to see whether it would make a difference. The new error was as shown below.
Atom: 1.14.4 x64 Electron: 1.3.13 OS: Mac OS X 10.12.3 Thrown From: markdown-themeable-pdf package 1.2.0
Stack Trace
Failed to activate the markdown-themeable-pdf package
Commands
Non-Core Packages