Use with Webpack about mojs HOT 19 CLOSED

import mojs from 'mojs' worked for me

from mojs.

mojs is a different library when loaded via NPM
https://www.npmjs.com/package/mojs

I am doing npm install mo-js --save as describe above which pulls it from: https://www.npmjs.com/package/mo-js

And if I do import mojs from 'mo-js' the mojs object is empty.

how are you loading it?

from mojs.

I didn't test it in-depth, but it returned an object:
npm install mo-js
then
import mojs from 'mojs';

from mojs.

Maybe you have https://www.npmjs.com/package/mojs globally installed.

from mojs.

Looks like I do. Sorry!

from mojs.

@roundrobin hi, sorry about that! I've just rechecked and yes we have the problem with es2015 modules and even with require statements. I've solved the issue but need a drip more tests to ensure it works everywhere. Will try to push the hotfix to the master branch tomorrow.

Thank you so much for heads up and sorry again. Cheers

from mojs.

Awesome @legomushroom That would be amazing. I am happy to test it then #GoEs2015

from mojs.

@roundrobin just released the 0.265.8 version that should fix the issue. Please let me now if doesn't work for you.

from mojs.

Thanks @legomushroom it works for me! Although only with require('mo-js') syntax, when using import statement, it doesnt work.

Thanks for the fast fix 💯

from mojs.

@roundrobin hm it worked for me with import just fine. Could you check this project in the attached archive and confirm if it works for you? Archive.zip

from mojs.

I am occasionally getting "mojs is undefined" errors thrown from helpers with a codepen copied example:

mo.js:5370 Uncaught ReferenceError: mojs is not defined

Helpers.prototype.error = function() {
  if (mojs.isDebug === false) {
    return;
  }
  return console.error.apply(console, this.prepareForLog(arguments));
};

mo.js definitely works with es6 imports, I have it working with mojs.Burst, I've just had the helper mojs reference error thrown in a few instances.

THIS LIBRARY ROCKS! Nice work legomushroom!

from mojs.

@hyperbrave ah that's bad. was rushing to release the fix. You are using the latest release, right?

from mojs.

@legomushroom

"mo-js": "^0.265.8",

The reference error is definitely not always occurring, only a few times. I encountered it initially while trying to copypasta this example. http://codepen.io/sol0mka/pen/pbRejJ

It is thrown always when using an invalid value in burst children options.

new mojs.Burst({
  children: {
     // oops 
    shape: ["triangle"],
  }
})

from mojs.

@hyperbrave thanks! Please use the version 0.265.6 for now, I'll try to fix that asap.

from mojs.

@hyperbrave made 0.265.9 release with the fix, if you use jsdelivr / bower to install the library might need some time to show up on their website. Hope it helps!

from mojs.

@legomushroom thanks! 0.265.9 no mojs reference error thrown by helpers, and a useful log message for invalid shapes!

mo.js:5376 mo·js no "triangle" shape available yet, please choose from this list: ["circle", "line", "zigzag", "rect", "polygon", "cross", "equal", "curve"]

from mojs.

@hyperbrave happy to help! 😊

from mojs.

"mo-js": "^0.288.2" version I am facing same issue

from mojs.

Hi @SuneethaYamani,

You should now use the lastest release from the NPM org.:
import mojs from '@mojs/core'

Check the official documentation at https://mojs.github.io/tutorials/getting-started.html#setup-mo-js-in-your-project.

😉

from mojs.