-
Notifications
You must be signed in to change notification settings - Fork 85
Uncaught Error: Undefined nameToPath for hyperapp #421
Comments
I cloned this to Github and tested it locally on my machine, and was able to get it to compile (though that's not the same as working, hyperapp still doesn't seem to mount and render, just no compiler errors happen). My local Node install is newer though:
Wondering if this is an issue with the Node/NPM versions, or some specific issue with the Glitch environment. |
on advisement from IRC, I tried a much simpler module, to eliminate as many variables as possible. I can confirm this works offline with the versions above, but not on Glitch's older version: https://glitch.com/edit/#!/curved-prawn I've cloned this version to Github as well: https://github.com/jarcane/cljs-on-glitch-2 |
I've also opened a topic on the Glitch Discourse, as this seems more and more like it's probably specifically related to how Glitch handles npm dependencies. https://support.glitch.com/t/lumo-cljs-and-glitch-pnpm-issue/5283 |
OK, I can now reproduce this locally under Ubuntu/WSL. The issue seems to be caused by however pnpm handles modules that differs from normal npm. The compiler also throws a fun new error to stdio I don't recall seeing on Glitch that further points to a resolver issue:
|
Did you solve this? |
The pnpm folks suggested a workaround that works locally, though we've yet to solve it for Glitch. The pnpm issue suggests its the result of some of the lumo dependencies:
But did not elaborate further. |
Version: 1.8.0, 1.9.0-alpha
I'm working on building a Glitch template project for CLJS, and I've got as far as getting CLJS itself to compile fine, but I don't seem to be able to get NPM modules to work.
According to the blogs here and here it seems like I should just be able to
:require
them but instead I get this:The WIP project is public so you can see it here: https://glitch.com/edit/#!/wise-feet
Relevant files: build.cljs, package.json, and main.cljs (note: the code in
app.main
itself possibly doesn't work yet either, but it doesn't get that far as it fails on the require).I've tried using both node and the
:install-deps
option to handle the dependencies but I get the same problem regardless.The text was updated successfully, but these errors were encountered: