Skip to content
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

Using with Webpack #37

Open
dschissler opened this issue Mar 1, 2015 · 4 comments
Open

Using with Webpack #37

dschissler opened this issue Mar 1, 2015 · 4 comments

Comments

@dschissler
Copy link

Has anyone been able to get this working with Webpack? I tried shimming it but I'm not sure what is going wrong. It was complaining about not being able to find the parent. In fact, none of the require calls were working inside of it.

@dschissler
Copy link
Author

I wasn't able to get this working with the npm package. I used the bower package and I'm using the coffeescript source with a change to the require line.

Backbone = @Backbone or window?.Backbone or (try require?('backbone')) or (try require?('exoskeleton')) or null

simply becomes:

Backbone = require 'backbone'

It seems like the conventional way to load alternatives like Exoskeleton and Lodash is to create an alias in the webpack config.

@dschissler
Copy link
Author

Also, I've created a new internal package with just the coffeescript file because the 50KB file is pulling in 2.7MB of hard wired dependencies such as Backbone, Underscore, Jquery, etc. I just don't need to be downloading that many extra files and it since I'm traveling I can't always be sure of th quality of my Internet connection and I need to be able to easily do a fresh npm install.

@dschissler
Copy link
Author

Has anyone considered removing the shims from query-engine and making the bundler take care of that instead? It seems to me that it is the responsibility of the bundler tool like requirejs, webpack and browserify to wire up a API compatible clone like Exoskeleton.

@balupton
Copy link
Member

Will be addressed with #43

@balupton balupton self-assigned this Feb 26, 2016
@balupton balupton removed their assignment Apr 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants