-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use project with browserify / frontend tools #2
Comments
This is a node.js-based project. It is mostly used as a grunt plugin in an asset pipeline. I have no idea how browserify helps in any of that. The project is to produce image bitmap sprites for the browser, not in the browser. Could you share more on what you are trying to achieve, and the exact setup to reproduce the problem? |
Right now I'm using bin-pack to do real-time sprite sheeting in the browser (client-side) rather than having to do it as an offline step. This is useful, for example, when packing dynamic light maps into a single texture for the GPU with WebGL. However, your module seems like it could pack much more efficiently than Browserify (like webpack) is just a way to utilize these npm modules in client-side code without all the grunt/gulp tasks. For example, const binPack = require('bin-pack');
const result = binPack([ { width: 120, height: 100 }, ... ]);
console.log(result); Running browserify from shell: browserify pack.js --debug > bundle.js Now the |
IC. So how can I repro the problem the easy way? Is it enough to |
Note to myself: browserify is a static code converter. It is likely having a problem with dynamic UMD prologues used by |
Not sure what's up with the installation and why
heya-ctr
is really needed (there are probably more robust & well tested binary/quick sort libs on npm?), but I'm getting this error trying to use either entry point:Too bad since this seems like it could be a really handy module! Thanks for writing it anyways. 😄
The text was updated successfully, but these errors were encountered: