Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Anachron
@Anachron
For the smallest applications it may work, but everything in a respectable size won't, that's the whole point build-tools like mimosa, grunt and gulp exist.
hahahahahahahahahahahahahahahaha
@hahahahahahahahahahahahahahahaha
Agree with @Anachron , dude lives on the streets of SF probably
hahahahahahahahahahahahahahahaha
@hahahahahahahahahahahahahahahaha
btw, has anyone tried to integrate Mimosa with LiveStyle + Stylus + LiveReload?
David Bashford
@dbashford
I've not used LiveStyle before myself
hahahahahahahahahahahahahahahaha
@hahahahahahahahahahahahahahahaha
neither have I, was checking it out and was interested, Mimosa is good in my book :) for anything like that, I think you're looking at diminishing returns if you're talking about saving from the inspector back into the files, I mean the concept is pretty sexy, but at the moment its a bit of an edge case
Sam Armstrong
@DrSammyD
jrburke/r.js#629
huzah!
David Bashford
@dbashford
thats awesome =) Now need to find time to dig into dealing with that.
Samuel Laulhau
@lalop
Hello,
I start to work on a new project build with mimosa
so I discover it
I have "some" issue to make require work on build but I didn't see any configuration on it
First error come from main.coffee requiring ./common that is in the same folder at the build I get this error
....
oups I'm wrong ./common is found but not jquery
How do I specify the vendor path ?
David Bashford
@dbashford
that's a require.js thing, you have in your common.js a path that routes to jquery. like "jquery":"vendor/jquery/jquery"
Samuel Laulhau
@lalop
I have something like that in common.coffee but I tried to log the config and nothing is outputed on build
Samuel Laulhau
@lalop
in fact it's like if the require configuration in common.coffee isn't loaded at build time
Samuel Laulhau
@lalop
I fixed my issue, in fact in common.coffee I built my config dynamically by looping over an array of library name.
Apparently the configuration have to be righten explicitely
David Bashford
@dbashford
If you run mimosa build -ompD then you'll see the r.js config options if that is what you are looking for. Its the -D that does it.
David Bashford
@dbashford
Replying here to a question that @boltforge asked me, I've essentially been stalled for 2 reasons, 1) writing a million tests burned me out a bit and 2) I've had a ton of other things sucking up my time. If anyone wanted to help, it would be in writing tests for the things that are still in CoffeeScript (if they have been converted to .js that means they have had tests written). Once the tests are knocked out I'd be able to focus on a few key features for 3.0 before releasing it. Despite it being 3.0, all the work was started in a 2point4 branch, which is where it lives now.
David Bashford
@dbashford
That said, the tests require a lot to just get up to speed with how they work, and its testing, so not the most fun thing to jump in and help with. =)
hahahahahahahahahahahahahahahaha
@hahahahahahahahahahahahahahahaha
yeah, these are a little intense, I can see why you may have become a little burned out from this much single-handedly
David Bashford
@dbashford
Been doing more mimosa related stuff the last few weeks specifically in support of my team, so I'm slowing getting back into the swing of things. I won't make any promises but given my work is going to slow down some, I hope to at least wrap up tests before the end of July. Considering the template compiler was 1200 lines, and I've still got some of the bigger things to test, good chance it goes beyond that.
Anachron
@Anachron
Take your time, I'm having bash projects right now, so I am kinda out of web business for now. :)
hahahahahahahahahahahahahahahaha
@hahahahahahahahahahahahahahahaha
I keep getting this error, any advice for tracking it down? Using node 0.12.4. Any ideas for what the root cause of this, last time bumping the version of mimosa-live-reload.
"mimosa": "2.3.20",
    "mimosa-jade": "2.3.0",
    "mimosa-live-reload": "1.4.0",
    "mimosa-post-hook": "0.3.0",
    "mimosa-server-reload": "1.1.0",
    "mimosa-server-template-compile": "^0.7.0",
    "mimosa-stylus": "1.4.0",
    "mimosa-web-package": "2.0.0",
[Error: Module did not self-register.]
js-bson: Failed to load c++ bson extension, using pure JS version
[Error: Module did not self-register.]
js-bson: Failed to load c++ bson extension, using pure JS version
[Error: Module did not self-register.]
js-bson: Failed to load c++ bson extension, using pure JS version
[Error: Module did not self-register.]
js-bson: Failed to load c++ bson extension, using pure JS version
[Error: Module did not self-register.]
js-bson: Failed to load c++ bson extension, using pure JS version
21:44:03 - Success - Mimosa is starting your server: server.js
mongohq
/node_modules/bcrypt/node_modules/bindings/bindings.js:83
hahahahahahahahahahahahahahahaha
@hahahahahahahahahahahahahahahaha
nvm might have it isolated
so 100% bcrypt related....
hahahahahahahahahahahahahahahaha
@hahahahahahahahahahahahahahahaha
so, for anyone that runs into this who happens to be using bcrypt, this seems to be the simple solution: http://stackoverflow.com/questions/29320201/error-installing-bcrypt-with-npm
Anachron
@Anachron
Thanks for sharing the solution! :)
hahahahahahahahahahahahahahahaha
@hahahahahahahahahahahahahahahaha
no prob! :shipit:
:smile:
Ghost
@ghost~54f494ed15522ed4b3dcafad

@dbashford I am planning to release the copy-all module soon and because it's based on the copy module, I want to know what license does it have so I can license my module accordingly.

Thanks

David Bashford
@dbashford
@dpeukert I don't pay much attention to license. Is free for all to use any way they see fit. MIT is fine.
Ghost
@ghost~54f494ed15522ed4b3dcafad
Alright, thanks.
Ghost
@ghost~54f494ed15522ed4b3dcafad
David Bashford
@dbashford
woot! good stuff
hahahahahahahahahahahahahahahaha
@hahahahahahahahahahahahahahahaha
does anyone have anything like munch working with Mimosa?
Anachron
@Anachron
Nope.
hahahahahahahahahahahahahahahaha
@hahahahahahahahahahahahahahahaha
well...it's been real Mimosa peoples
David Bashford
@dbashford
:+1:
Anachron
@Anachron
I may have a private project, but it doesn't have high requirements :)
developermalik
@developermalik
Hi, can I get some advice here please. I need to change a gui on a mimosa project. How do I go about this. Changes required are generally buttons widgets and also a search bar. The CSS changes ruin the entire website because of the grid layout being used. Thank you in advance
Anachron
@Anachron
mimosa is a build workflow tool, has nothing to do with css or anything like that. do you have the code somewhere?
Anachron
@Anachron
It's interesting to find out that webpack actually tries to be somewhat similar to mimosa in some ways.
David Bashford
@dbashford
I've been using webpack myself. (Very odd for me to be using another build tool) And yeah, lots of similarities. Seeing them in other places too. We are considering moving to ember-cli for our app, just because that is where the ember community has entirely gone too, and some of the broccoli stuff resembles mimosa as well. I have definitely enjoyed digging around other things for once. =)
Anachron
@Anachron
Well honestly you could help those webpack builders somewhat :P few t hings make trouble
puck7744
@puck7744
Hey, I'm starting a small web app project and I picked Mimosa because it seemed like a good all around starting point, but I'm brand new to node.js in general and I'm a baffled by the templating paradigm. I picked Dust for both types of template but I can't get client-side templates to work. The documentation for Dust says to use dust.compile, dust.render(), etc but my browser's developer console tells me that "dust" is undefined.