Coder Social home page Coder Social logo

Comments (16)

mitar avatar mitar commented on June 10, 2024

I think you are not using the latest package. Please check which version of the package you are using. Please provide a small reproduction.

from meteor-blaze-components.

hexsprite avatar hexsprite commented on June 10, 2024

I'm using 0.23.0

I tried a reproduction using meteor create --bare; meteor remove static-html; meteor add peerlibrary:blaze-components

But it doesn't seem to happen. I checked and all the packages installed in versions in the repro are the same in my project. So I'm a little confused since the error is being reported as peerlibrary:blaze-components

from meteor-blaze-components.

mitar avatar mitar commented on June 10, 2024

From my experience I think you are not really using 0.23.0. Can you check in versions file?

from meteor-blaze-components.

hexsprite avatar hexsprite commented on June 10, 2024

peerlibrary:[email protected]

from meteor-blaze-components.

mitar avatar mitar commented on June 10, 2024

Hm, then I do not have an idea. Without reproduction I cannot really help much here. :-(

Maybe some other PeerLibrary dependency is not at the latest version.

from meteor-blaze-components.

hexsprite avatar hexsprite commented on June 10, 2024

OK I took the packages from from my large app and copied it into a new project. Seems to reproduce this issue but I'm not yet sure why...

https://github.com/hexsprite/meteor-blaze-components-156

from meteor-blaze-components.

mitar avatar mitar commented on June 10, 2024

Have you went through all peerlibrary packages in versions and made sure they are at the latest version?

from meteor-blaze-components.

hexsprite avatar hexsprite commented on June 10, 2024

Have you went through all peerlibrary packages in versions and made sure they are at the latest version?

Yup.

from meteor-blaze-components.

mitar avatar mitar commented on June 10, 2024

I am not sure when I will have time too look into this. I thought this has been resolved by re-publishing all packages.

You could try putting them temporary into packages/ inside your app, and see if that resolves it. And if does, then bisect to see which one has to be there. And then I can look if I maybe missed some to republish.

from meteor-blaze-components.

hexsprite avatar hexsprite commented on June 10, 2024

Thanks, I'm going to be busy with some other issues but I will return to this and let you know what I figure out... I suspect something is pulling in an old dependency...

from meteor-blaze-components.

mitar avatar mitar commented on June 10, 2024

I suspect something is pulling in an old dependency...

But you would see that in .versions file I believe.

from meteor-blaze-components.

hexsprite avatar hexsprite commented on June 10, 2024

I've been checking dependencies using meteor list --tree but I don't notice anything obvious.

As a workaround I forked the package and added meteorBabelHelpers = Package.modules.meteorBabelHelpers at the top of lib.coffee and that has fixed the problem for now.

I audited all the built packages and found that also peerlibrary:base-component was also missing the meteorBabelHelpers declaration.

from meteor-blaze-components.

hexsprite avatar hexsprite commented on June 10, 2024

I'm curious by which mechanism that Meteor decides that a given package requires the a particular dependency declaration to be added... seems like something is broken there...

from meteor-blaze-components.

mitar avatar mitar commented on June 10, 2024

They are using dependency resolver, computing the solution for all dependency constraints. So something is pushing an old version.

Have you tried cloning repositories into packages? From my experience that should be enough and no need to change the code in a forked repo?

from meteor-blaze-components.

hexsprite avatar hexsprite commented on June 10, 2024

Have you tried cloning repositories into packages? From my experience that should be enough and no need to change the code in a forked repo?

Yes. It did not help. I had to add the declaration in order to get it to work.

from meteor-blaze-components.

MatejJan avatar MatejJan commented on June 10, 2024

Bumping this as I also ran into the same or a very similar issue when building for cordova/electron (web version works just fine).

Uncaught ReferenceError: meteorBabelHelpers is not defined
    at lib.coffee:1131

from meteor-blaze-components.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.