Not possible to require or import?

I switched to this maintained library from the old one. Just doing the switch, I am no longer able to use a standard const brain = require('brain.js') (I basically just changed from brain to brain.js in the require), because the module will not be exported but put on the global window variable.

Is there a reason for this? For now I just access the library using window.brain, but it would be nice to actually import/require the module to achieve a modern build process using e.g. webpack.

Any info on this and explanation why it is done this way would be nice.

//edit: I’m using brain inside the browser, I also tried brain.js/browser and it is also adding brain to window instead of exporting it.

[robertleeplummerjr]

I believe this is now resolved. @michaelsanford the library uses (at least I looked) import { xxx } from whatever;, (src/neural-network.js, for example) but does not in index.js which gets files from ./dist, which are es5.

If you’d like to use the es6 files, simply use import brain from 'brain.js/src'; or import brain from 'brain.js/src/index'; I think.

@robertleeplummerjr If you’ve not yet gotten around to it, I’d be interested in working on this.

I didn’t see that till it was too late. Feel free to check the wiki, the direction, and any outstanding bugs. Committers & forks are wanted and loved.

Ty!

[matthewjumpsoffbuildings]

When using in node, I’m still getting TypeError: brain.NeuralNetwork is not a constructor when I do

const brain = require('brain.js')
const net = new brain.NeuralNetwork()

It turns out that, for some bizzare reason, the export from brain.js is this

{
  brain: { ...brain class },
  default: { ...brain class again? }
}

So in order to get it working properly, you should do

const brain = require('brain.js').brain // redundant access to nested object
const net = new brain.NeuralNetwork()