I am stuck in the same place. I have tried three or four different
suggestions from stackoverflow and google.
Chris
npm run dev
> leo-vue@1.4.0 dev /home/chris/leo-editor/leovue
> node build/dev-server.js
ERROR Failed to compile with 1 errors 11:19:15 AM
error in ./src/main.js
Module build failed: Error: Couldn't find preset "es2015" relative to
directory "/home/chris/leo-editor/leovue"
at
/home/chris/leo-editor/leovue/node_modules/babel-core/lib/transformation/file/options/option-manager.js:293:19
at Array.map (native)
at OptionManager.resolvePresets
(/home/chris/leo-editor/leovue/node_modules/babel-core/lib/transformation/file/options/option-manager.js:275:20)
at OptionManager.mergePresets
(/home/chris/leo-editor/leovue/node_modules/babel-core/lib/transformation/file/options/option-manager.js:264:10)
at OptionManager.mergeOptions
(/home/chris/leo-editor/leovue/node_modules/babel-core/lib/transformation/file/options/option-manager.js:249:14)
at OptionManager.init
(/home/chris/leo-editor/leovue/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
at File.initOptions
(/home/chris/leo-editor/leovue/node_modules/babel-core/lib/transformation/file/index.js:212:65)
at new File
(/home/chris/leo-editor/leovue/node_modules/babel-core/lib/transformation/file/index.js:135:24)
at Pipeline.transform
(/home/chris/leo-editor/leovue/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
at transpile
(/home/chris/leo-editor/leovue/node_modules/babel-loader/lib/index.js:50:20)
at Object.module.exports
(/home/chris/leo-editor/leovue/node_modules/babel-loader/lib/index.js:175:20)
@ multi ./build/dev-client ./src/main.js
> Listening at http://localhost:8080
On Thu, Jan 4, 2018 at 11:10 AM, Kent Tenney <kten...@gmail.com> wrote:
> I also see
> Cannot GET /
>
> at localhost:8080
> and the following in the terminal where I entered
> $ npm run dev
>
> ERROR Failed to compile with 1 errors
>
> 1:08:24 PM
>
> error in ./src/main.js
>
> Module build failed: Error: Couldn't find preset "es2015" relative to
> directory "/opt/fetching/leovue"
> at /opt/fetching/leovue/node_modules/babel-core/lib/
> transformation/file/options/option-manager.js:293:19
> at Array.map (native)
> at OptionManager.resolvePresets (/opt/fetching/leovue/node_
> modules/babel-core/lib/transformation/file/options/
> option-manager.js:275:20)
> at OptionManager.mergePresets (/opt/fetching/leovue/node_
> modules/babel-core/lib/transformation/file/options/
> option-manager.js:264:10)
> at OptionManager.mergeOptions (/opt/fetching/leovue/node_
> modules/babel-core/lib/transformation/file/options/
> option-manager.js:249:14)
> at OptionManager.init (/opt/fetching/leovue/node_
> modules/babel-core/lib/transformation/file/options/
> option-manager.js:368:12)
> at File.initOptions (/opt/fetching/leovue/node_modules/babel-core/lib/
> transformation/file/index.js:212:65)
> at new File (/opt/fetching/leovue/node_modules/babel-core/lib/
> transformation/file/index.js:135:24)
> at Pipeline.transform (/opt/fetching/leovue/node_
> modules/babel-core/lib/transformation/pipeline.js:46:16)
> at transpile (/opt/fetching/leovue/node_modules/babel-loader/lib/
> index.js:50:20)
> at Object.module.exports (/opt/fetching/leovue/node_
> modules/babel-loader/lib/index.js:175:20)
>
> @ multi ./build/dev-client ./src/main.js
>
> > Listening at http://localhost:8080
>
>
>
> On Wed, Jan 3, 2018 at 8:00 PM, Chris George <technat...@gmail.com> wrote:
>
>> I am on Day 2 of trying to get it to work on my system. It took over a
>> week last time, but I have since installed a different Linux distribution.
>> Today I finally got "npm run dev" to work without errors.
>>
>> Now to figure out what "Cannot GET /"means, :-(
>>
>> Chris
>>
>> On Wed, Jan 3, 2018 at 3:29 PM, Joe Orr <joe....@gmail.com> wrote:
>>
>>> Offray,
>>>
>>> Thanks for the kind words. About Electron, that is basically just node +
>>> browser in a package. I think should be doable to wrap Leo python code in
>>> node and have the browser interface, maybe using something like this:
>>> https://www.npmjs.com/package/node-python
>>>
>>> About other formats and outlines, no plans for that. People can always
>>> just import into Leo ;-)
>>>
>>> Joe
>>>
>>>
>>> On Wednesday, January 3, 2018 at 2:50:14 PM UTC-5, Offray Vladimir Luna
>>> Cárdenas wrote:
>>>
>>>> Joe,
>>>>
>>>> The web interface looks really great. I wonder if this could be the
>>>> path for the visualization & services 2018 roadmap. The advantage of using
>>>> a web interface as a rendering interface is that a lot of stuff is there
>>>> ready to be used. Electron apps [1] has been discussed previously in this
>>>> list as a possibility for such integration, but I don't know you they can
>>>> use the python source there.
>>>>
>>>> [1] https://github.com/electron/electron
>>>>
>>>> There is any support for OPML or other ouliners? I think this could be
>>>> a really good way to publish online the output of several programs.
>>>>
>>>> Keep the good work.
>>>>
>>>> Cheers,
>>>>
>>>> Offray
>>>>
>>>> On 03/01/18 09:23, Joe Orr wrote:
>>>>
>>>> Forgot to add, so far I haven't posted about Leo Vue anywhere but here
>>>> because it was missing key features. The basic features are now complete so
>>>> I'll be posting about it elsewhere in a few weeks. In meantime, if anyone
>>>> has a bug report, that would be very helpful, the program isn't very well
>>>> tested yet. Also if anyone has a nice sample Leo file to post to the
>>>> examples repo, that would be great as well. You can load your leo file just
>>>> by using the index.html file noted in the README.
>>>>
>>>> Joe
>>>>
>>>> On Wednesday, January 3, 2018 at 9:19:17 AM UTC-5, Joe Orr wrote:
>>>>>
>>>>> Edward,
>>>>>
>>>>> Thanks for the note, will be adding to the README soon, including an
>>>>> acknowledgement to you for making it all possible.
>>>>>
>>>>> Couple of notes about making a front end for Leo using web
>>>>> technologies:
>>>>> - I can make the tree look exactly like the current Leo interface with
>>>>> basically just CSS, will add that as option in future.
>>>>> - Vue is a great framework for this, lightweight and complete. Leo Vue
>>>>> is a good case study, I think. Will be adding more (Leo) docs to explain
>>>>> the code.
>>>>> - The reader program has some capabilities that wouldn't be suitable
>>>>> to the actual program, like being able to load subtrees. So a Leo version
>>>>> with a web interface would be separate program, not an extension of Leo
>>>>> Vue. But a lot of the same code or patterns could be used.
>>>>> - Mentioned this way back when but haven't had time to work on it, the
>>>>> Leo (python) program could be wrapped in node, and web front end could
>>>>> talk
>>>>> to it.
>>>>>
>>>>> Joe
>>>>>
>>>>> On Tuesday, January 2, 2018 at 8:27:45 PM UTC-5, Edward K. Ream wrote:
>>>>>>
>>>>>> On Mon, Jan 1, 2018 at 5:08 PM, Joe Orr <joe...@gmail.com> wrote:
>>>>>>
>>>>>>> The Leo HTML viewer is now Leo Vue - added more Vue integration.
>>>>>>>
>>>>>>> https://github.com/kaleguy/leovue
>>>>>>>
>>>>>>
>>>>>> Many thanks, Joe, for this outstanding work.
>>>>>>
>>>>>> For those following this link, please make sure you scroll down the
>>>>>> page. There you will see the readme.md
>>>>>> <https://github.com/kaleguy/leovue/blob/master/README.md> file. It
>>>>>> shows the impressive capabilities of the viewer and provides a
>>>>>> spectacular
>>>>>> demo of Leo. I'd like to make this "presentation" part of Leo's home
>>>>>> page.
>>>>>>
>>>>>> Joe, Leo Vue already goes far beyond what I had hoped in terms of a
>>>>>> web interface for Leo. I shall be studying the code closely, focusing on
>>>>>> reveal.js, vue.js, and the other dependencies in package.json. This
>>>>>> promises to save me months of aimless wandering.
>>>>>>
>>>>>> Edward
>>>>>>
>>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "leo-editor" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to leo-editor+...@googlegroups.com.
>>>> To post to this group, send email to leo-e...@googlegroups.com.
>>>> Visit this group at https://groups.google.com/group/leo-editor.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>>
>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "leo-editor" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to leo-editor+unsubscr...@googlegroups.com.
>>> To post to this group, send email to leo-editor@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/leo-editor.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "leo-editor" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to leo-editor+unsubscr...@googlegroups.com.
>> To post to this group, send email to leo-editor@googlegroups.com.
>> Visit this group at https://groups.google.com/group/leo-editor.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "leo-editor" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to leo-editor+unsubscr...@googlegroups.com.
> To post to this group, send email to leo-editor@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
