After upgrade to 1.1.0, the module cannot be imported about mmap-io HOT 7 CLOSED

In addition to fixing the main field in package.json, I had to edit mmap-io.js since it refers to a nonexistent es-release directory. Changing this to Release allowed the import to succeed on my system.

from mmap-io.

In package.json replace all "es-release" with "Release".
In nmap-io.js replace "es-release" with "Release".
In tsconfig.json replace "es-release" with "Release".
In package.json add "main": "mmap-io.js"

from mmap-io.

Sorry I didn't see the github notifications earlier, fixed and updated. Holler and tag me if you have any problems!

from mmap-io.

Sorry, this is not fixed yet. The build artifact live in build/Release because you use node-gyp (as you should), but mmap-io.js imports build/es-release/mmap-io.
See an example of build failure: https://travis-ci.com/stanford-oval/genie-toolkit/builds/118448865 (from greenkeeper trying the new build on my project)

from mmap-io.

(tagging @ozra as requested)

from mmap-io.

Alright, I'll go over it again, I'll dig up some of my old Quant-projects that use it heavily, and see how it behaves and get it right.

from mmap-io.

So...

1. the es-release files where black-listed and therefor not packaged into the npm
2. when they got with, they where wiped out on installment when the binary was rebuilt

• turns out just getting rid of the Makefile caused more crap than I ever had imagined, this actually took longer to get straight than rewriting the horror-show V8-code [ed: because they break compatibility every few months ] xD

Anyway, the js-files are now built into "dist" instead, and the binary into "build" as before, to keep them separated and thereby allow them to be built pre-publish and avoid unnecessary dependencies for the end-user, as intended.

Well. Should shit still roar up — just tag and shout out. Your project seems really cool by the way! I've bookmarked it along with a trail of others I found from it. For "when there is time" xD

Cheers!

from mmap-io.