Just a thought; shouldn't this be available through native Elm package management?
Le lundi 30 janvier 2017 08:23:09 UTC+1, Peter Damoc a écrit : > > > > On Mon, Jan 30, 2017 at 8:48 AM, Lyle Kopnicky <[email protected] > <javascript:>> wrote: > >> So I wonder if I can use elm-package to install a package from another >> directory, so hopefully the references will work out right? >> > > elm-package does not support that BUT, elm-github-install > <https://github.com/gdotdesign/elm-github-install> was designed for such > contexts. > Add the package manually to your dependencies and then use > elm-github-install to install it. > > >> when I build my project, because I'm using the default project URL, it >> gets referenced as _user$project$Native_KaTeX, which doesn't match. > > > You need a valid github project. Default values don't work. So, if you > fork the project and replace the user in that Native function name, you > should be able to compile it just fine. > > >> Another possibility is given by looking at >> https://github.com/eeue56/take-home/wiki/Writing-your-first-Elm-Native-module. >> >> Here the author shows some very different boilerplate, which doesn't seem >> to involve the project name in the variable names. I'd have to copy the >> elm-katex code into my own project and tweak it a bit, but that's OK for >> now as I'll only be building/running my project locally for the foreseeable >> future. Also I'd be able to update the version of KaTeX that's embedded in >> the file. >> > > The guide you referenced is for an old way to do Native. That API is > obsolete. > > > -- > There is NO FATE, we are the creators. > blog: http://damoc.ro/ > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
