-
Notifications
You must be signed in to change notification settings - Fork 17.4k
Uncaught Error: ENOENT, node_modules/typescript/lib/lib.d.ts not found in /usr/share/atom/resourc... #22455
Comments
Similar to #22432 |
Is there a workaround for this? |
not that I've found. |
Maybe go to Note: Prerequisite: |
That's a workaround for me, but not for my users. How come tslib is loaded at all? I don't require it in my source, and all typescript related stuff is in dev dependencies. |
Adding typescript to the regular dependencies doesn't help. |
Idk. Maybe try |
That gives me
this bit seems strange to me:
not only is that a path on my local disk, ( |
That seems like a completely different error: the stacktrace says it comes from EDIT: Wait, since Line 72 in 9826355
This is dev-mode, so probably Lines 57 to 58 in 9826355
Edit: It thinks you're testing the clone of atom instead of your actual atom - simply move to the actual atom directory. |
I don't follow? I didn't clone atom, I've just installed it, and I'm working in my package dir. When I
|
Yes, it's doing the wrong atom, maybe |
What would be the correct atom directory? I don't need the source of atom cloned to develop an addon, right? I'm working in the clone of my addon (https://github.com/retorquere/zotero-citations/) I'm on MacOS BTW. I've renamed the directory of my addon clone to
and same as before, when I |
Wow, this debugging is super weird. Note: I think what's happening is that atom is |
That would mean |
Oh, I added |
|
This is good? |
Yes Edit: This was so trivial I shouldn't've needed the better stacktraces. Thanks though |
The above stack trace was in-app, this was written to the terminal where I started console log
|
A "simple" fix would be to just do After doing As I finished typing it went to 46% Anyways, Either way, This also happens to be a start for implementing my idea at #22517 (comment). |
I've added Is there a way to tell |
The problem is that atom itself needs to install typescript as a dependency - there's not anything wrong with your repository |
But another option would be to publish only the generated javascript, right? I could just rename the ts files to something else so they wouldn't be picked up by atom. |
Yeah, I think that would work. Should I open another issue for this then? |
No, the current issue is fine, the renaming would be a workaround I'd want to get rid of. |
typescript does not tolerate different file extensions unfortunately. |
I've created a custom compiler using the TS library, and that works, but this is something I'd want to be rid of. It's only a workaround. |
Reproduction Steps:
zotero-citations
.Atom: 1.57.0 x64
Electron: 9.4.4
OS: Ubuntu 20.04.2
Thrown From: Atom Core
Stack Trace
Uncaught Error: ENOENT, node_modules/typescript/lib/lib.d.ts not found in /usr/share/atom/resources/app.asar
Commands
Non-Core Packages
The text was updated successfully, but these errors were encountered: