Re: [elm-discuss] Mysterious failure to find packages during compilation

2017-06-18 Thread Ilias Van Peer 
Yeah, this could be caused by "conflicting packages" - seems like you may 
have been using a different package that has a dependency on 
`elm-community/json-extra`, which uses the same module names as (and 
supersedes) `elm-community/elm-json-extra`.

Op zondag 18 juni 2017 05:08:38 UTC+2 schreef erik aker:
>
> Hi, I had a similar problem today and it turned out to be related to a 
> particular package in my elm-package.json. I noticed that after I added 
> that package, which was "elm-community/elm-json-extra": "2.3.0 <= v < 
> 3.0.0", that I would get this error about elm-lang/navigation. If I removed 
> this seemingly unrelated package from the list, the error goes away. I 
> also, like you, removed elm-stuff and tried again.
>

-- 
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 elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [elm-discuss] Mysterious failure to find packages during compilation

2017-06-17 Thread erik aker 
Hi, I had a similar problem today and it turned out to be related to a 
particular package in my elm-package.json. I noticed that after I added 
that package, which was "elm-community/elm-json-extra": "2.3.0 <= v < 
3.0.0", that I would get this error about elm-lang/navigation. If I removed 
this seemingly unrelated package from the list, the error goes away. I 
also, like you, removed elm-stuff and tried again.


On Wednesday, February 22, 2017 at 11:13:51 PM UTC-8, Austin Bingham wrote:
>
> Sorry, I should have mentioned that originally. Yes, deleting elm-stuff 
> was the first thing we tried.
>
> On Wednesday, February 22, 2017 at 11:16:37 PM UTC+1, Noah Hall wrote:
>>
>> Did you try deleting the `elm-stuff `folder and trying again? 
>>
>> On Wed, Feb 22, 2017 at 6:11 PM, Austin Bingham 
>>  wrote: 
>> > I'm trying to sort out a compilation problem that I (really, a friend 
>> trying 
>> > to use my code) is seeing. In a nutshell, when he compiles my project 
>> he 
>> > sees this: 
>> > 
>> >  
>> > 
>> > ERROR in ./src/Main.elm 
>> > Module build failed: Error: Compiler process exited with error 
>> Compilation 
>> > failed 
>> > Could not find package elm-lang/navigation. 
>> > 
>> > Maybe your elm-stuff/ directory has been corrupted? You can usually fix 
>> > stuff 
>> > like this by deleting elm-stuff/ and rebuilding your project. 
>> > Packages configured successfully! 
>> > 
>> > at ChildProcess. 
>> > 
>> (/home/users/russel/Repositories/Git/Forks/ACCU_2017_Elm_App/node_modules/elm-webpack-loader/node_modules/node-elm-compiler/index.js:291:27)
>>  
>>
>> > at emitTwo (events.js:106:13) 
>> > at ChildProcess.emit (events.js:191:7) 
>> > at maybeClose (internal/child_process.js:877:16) 
>> > at Process.ChildProcess._handle.onexit 
>> (internal/child_process.js:226:5) 
>> >  @ ./src/index.js 10:10-31 
>> > 
>> >  
>> > 
>> > This is on a Debian 'sid' machine. The compilation is occurring via the 
>> > elm-webpack plugin, and all of the node/npm tool chain seems to be OK. 
>> The 
>> > build is known to work on OS X, and in fact it seems to work just fine 
>> on 
>> > another Debian 'sid' system, albeit one running inside virtualbox. 
>> > 
>> > After this error the elm-stuff directory exists but is empty. So I know 
>> it's 
>> > a long-shot, but does this ring a bell with anyone? Can you think of 
>> what 
>> > might cause this to happen? 
>> > 
>> > Austin 
>> > 
>> > -- 
>> > 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 elm-discuss...@googlegroups.com. 
>> > For more options, visit https://groups.google.com/d/optout. 
>>
>

-- 
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 elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [elm-discuss] Mysterious failure to find packages during compilation

2017-02-22 Thread Austin Bingham 
Sorry, I should have mentioned that originally. Yes, deleting elm-stuff was 
the first thing we tried.

On Wednesday, February 22, 2017 at 11:16:37 PM UTC+1, Noah Hall wrote:
>
> Did you try deleting the `elm-stuff `folder and trying again? 
>
> On Wed, Feb 22, 2017 at 6:11 PM, Austin Bingham 
>  wrote: 
> > I'm trying to sort out a compilation problem that I (really, a friend 
> trying 
> > to use my code) is seeing. In a nutshell, when he compiles my project he 
> > sees this: 
> > 
> >  
> > 
> > ERROR in ./src/Main.elm 
> > Module build failed: Error: Compiler process exited with error 
> Compilation 
> > failed 
> > Could not find package elm-lang/navigation. 
> > 
> > Maybe your elm-stuff/ directory has been corrupted? You can usually fix 
> > stuff 
> > like this by deleting elm-stuff/ and rebuilding your project. 
> > Packages configured successfully! 
> > 
> > at ChildProcess. 
> > 
> (/home/users/russel/Repositories/Git/Forks/ACCU_2017_Elm_App/node_modules/elm-webpack-loader/node_modules/node-elm-compiler/index.js:291:27)
>  
>
> > at emitTwo (events.js:106:13) 
> > at ChildProcess.emit (events.js:191:7) 
> > at maybeClose (internal/child_process.js:877:16) 
> > at Process.ChildProcess._handle.onexit 
> (internal/child_process.js:226:5) 
> >  @ ./src/index.js 10:10-31 
> > 
> >  
> > 
> > This is on a Debian 'sid' machine. The compilation is occurring via the 
> > elm-webpack plugin, and all of the node/npm tool chain seems to be OK. 
> The 
> > build is known to work on OS X, and in fact it seems to work just fine 
> on 
> > another Debian 'sid' system, albeit one running inside virtualbox. 
> > 
> > After this error the elm-stuff directory exists but is empty. So I know 
> it's 
> > a long-shot, but does this ring a bell with anyone? Can you think of 
> what 
> > might cause this to happen? 
> > 
> > Austin 
> > 
> > -- 
> > 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 elm-discuss...@googlegroups.com . 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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 elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[elm-discuss] Mysterious failure to find packages during compilation

2017-02-22 Thread Austin Bingham 
I'm trying to sort out a compilation problem that I (really, a friend 
trying to use my code) is seeing. In a nutshell, when he compiles my 
project he sees this:



ERROR in ./src/Main.elm
Module build failed: Error: Compiler process exited with error Compilation 
failed
Could not find package elm-lang/navigation.

Maybe your elm-stuff/ directory has been corrupted? You can usually fix 
stuff
like this by deleting elm-stuff/ and rebuilding your project.
Packages configured successfully!

at ChildProcess. 
(/home/users/russel/Repositories/Git/Forks/ACCU_2017_Elm_App/node_modules/elm-webpack-loader/node_modules/node-elm-compiler/index.js:291:27)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:877:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
 @ ./src/index.js 10:10-31



This is on a Debian 'sid' machine. The compilation is occurring via the 
elm-webpack plugin, and all of the node/npm tool chain seems to be OK. The 
build is known to work on OS X, and in fact it seems to work just fine on 
another Debian 'sid' system, albeit one running inside virtualbox.

After this error the elm-stuff directory exists but is empty. So I know 
it's a long-shot, but does this ring a bell with anyone? Can you think of 
what might cause this to happen?

Austin

-- 
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 elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.