Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 08 12:16
    L-IGH-T edited #1521
  • Feb 08 12:15
    L-IGH-T edited #1158
  • Jan 26 03:12
    L-IGH-T opened #1158
  • Jan 26 02:56
    L-IGH-T edited #1521
  • Nov 19 2020 02:37
    L-IGH-T edited #1521
  • Nov 19 2020 02:34
    L-IGH-T opened #1521
  • Sep 11 2020 05:59
    eben-roux closed #1014
  • Aug 17 2020 07:06
    frank-dspeed commented #1505
  • Jul 13 2020 13:04
    matthewp commented #1505
  • Jul 12 2020 09:08
    frank-dspeed commented #1505
  • Jul 12 2020 09:07
    frank-dspeed commented #1505
  • Jul 06 2020 20:02
    ivospinheiro commented #1520
  • Jul 06 2020 18:58
    matthewp commented #1520
  • Jul 06 2020 18:48
    ivospinheiro opened #1520
  • Jun 08 2020 16:44

    matthewp on master

    Add support for node 14 (modell… Try to generalize version Merge pull request #1157 from i… (compare)

  • Jun 08 2020 16:44
    matthewp closed #1157
  • Jun 08 2020 16:44
    matthewp commented #1157
  • Jun 06 2020 18:10
    icarito commented #1157
  • Jun 06 2020 18:05
    coveralls commented #1157
  • Jun 06 2020 18:04
    coveralls commented #1157
Paul Tichonczuk
@tracer99
is there any graceful way of rendering a stache template as a subtemplate in EJS? In mustache you simply did 
<%== can.view.render('template', object) %>
and this worked. however, if the template is a stache file (we're slowly converting), the output is [object DocumentFragment]
We found a workaround which is to use the element callback and manually appendChild ie
<%= (el)->el.appendChild(can.stache('template', object)) %>
This has drawbacks, not least of which is that we need a bunch of throw away containers.
Matthew Phillips
@matthewp
Yeah, I think the fact that ejs works with strings while stache uses fragments makes that the only real way
Paul Tichonczuk
@tracer99
@matthewp thanks
Paul Tichonczuk
@tracer99
So i'm back to trying to get paths to work in our older CanJS projects like DoneJS projects work. This project has had all it's libraries upgraded to the latest releases. The thing I'm after is being able to reference node_modules without having to specific "node_modules/" before every package.
I've set directotories: {src: "ucp2"} but that doesn't seem to make any change.
Kevin Phillips
@phillipskevin
you’ve set that under system?
if you’re loading steal from node_modules, it should automatically be able to find other node modules
Paul Tichonczuk
@tracer99
yes
and yes
Kevin Phillips
@phillipskevin
ok, I think you can only set directories.lib
Paul Tichonczuk
@tracer99
sorry
typo. it is lib
Kevin Phillips
@phillipskevin
ok
Paul Tichonczuk
@tracer99
I have like 8 paths entries that convert "package/package": "node_modules/package/package.js";
otherwise I get 404s for every node module imported
and luckily, none of those import other node modules
as it would fail
the issue I'm having now is getting steal-mocha working. as it does import other libraries and fails ....
package.json here: http://pastebin.com/ZvqHNTqs
Paul Tichonczuk
@tracer99
main script call <script type="text/javascript" src="/node_modules/steal/steal.js" main="ucp2/ucp2"></script>
Matthew Phillips
@matthewp
what error are you getting?
Justin Meyer
@justinbmeyer
contributors meeting: https://www.youtube.com/watch?v=1lU8s_B886c
Paul Tichonczuk
@tracer99
@matthewp 404s in the browser. So when I try to import 'chai'; the browser tries to load /chai/chai.js instead of /node_modules/chai/chai.js
I can create path entries for these, but it cascades down to every library that is imported and I'd need like 20 path entries.
Matthew Phillips
@matthewp
@tracer99 you have chai mapped to chai/chai
i think you don't need that configuration
Paul Tichonczuk
@tracer99
@matthewp that's just one example. steal-mocha same issue.
Julian
@pYr0x
@tracer99 can you try to use the latest steal 0.16.x version
if that will not help, maybe you can try steal 1.0
Here we used steal and chai also
https://github.com/donejs/job-cost-tracker/tree/master/public/components/data-cleanup/test
Justin Meyer
@justinbmeyer
So, I'm trying to explain the benefits of having CanJS broken out into individual repositories.
Presentation1.png
Currently, upgrading from CanJS 2.3 to 3.0 might look like that.
A big step.
Cursor_and_Presentation1.png
but if you break that step down ... CanJS 3.0 is mostly CanJS 2.3 ... with a lot of bug fixes, a lot of new features ... and some breaking changes (which account for most of the "step size"). Currently, to get all those bug fixes and new features ... you have to take on the breaking changes immediately and all at once.
Presentation1.png
Going forward, in CanJS 3.0, we'll be able to release packages independently of each other. This means you can keep upgrading to bug fixes and new features (small steps) ... and delay some of the big steps (can-route 4.0.0) until later.
Justin Meyer
@justinbmeyer
you'll be able to talk those big steps in pieces too. Say can-route 4.0 one month and can-component 4.0 another month
as can-route and can-component 4.0 are now independent of each other
and may depend on can-compute 3.X
Justin Meyer
@justinbmeyer
whoops
did I put this in stealjs!
Julian
@pYr0x
;)
WooFerPPK
@WooFerPPK
When in dev mode uploading a multipart form has the bounderies properly appended to the content type. However, the built version doesn't Instead, the boundary is in the Payload only. Our code "works" without errors, but uploads don't actually work as the boundary is not in the right place. How is the built version affecting the browsers behavior?
Matthew Phillips
@matthewp
No idea, very much doubt Steal has anything to do with that