-
-
Notifications
You must be signed in to change notification settings - Fork 485
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
Issue loading popover #172
Comments
@borysn can you please help us debug this? |
@justin808 I'll see what I can find. |
I'm having the exact same issue. @borysn did you find anything? |
Util in util.js has the same problem:
referenced code is in bootstrap file |
@razagill I tried to do some basic debugging just looking through the code, and poking around breakpoints with my project loaded up. I asked justin about how to debug an npm package properly, and he pointed me to a blog article, but I left off there. My guess right now is that the loader will struggle with any import statements. I'm going to try and get back to it, but I had a few interviews today, and I'm looking to prepare/move forward with those, so I may not have time. |
That is true.
The next line import Tooltip from './tooltip' is just ignored in dist. Tow options. Either reference originals or compile into single file as bootstrap did so that all variables available across modules. |
why do we use the files in dist and not in src?
this would work, but i'm not sure if it's the right way... |
Is there any workaround, guys? |
I can confirm that Utils fails when using only dropdown and itself, I couldn't find a workaround for now. |
Bootstrap moved away from UMD in Beta 4 twbs/bootstrap#20072. So the |
@borysn @razagill @frickt @Andre-Gl @Andrey-Pavlov @BenjaminSchubert This works, using bootstrap
@frickt You can remove that loader when using the above config. Make sure to Shame on them for releasing non-modular code in 2016. |
Is any PR needed for this issue? I'm glad to merge one in so long as at least one other person besides the PR author vouches for it. I won't have time to look at this for a couple of weeks. |
@justin808 I am not familiar enough with webpack loaders to know if it's possible to internalize the Hopefully they just bring back UMD. At the very least, the readme should be updated with the above information. |
Disclaimer: I'm a webpack & bootstrap newb. After some research, I don't see a way that a loader can add plugins to webpack cleanly. I think the best process may be placing the ProvidePlugin parameter object into a file, which would be included in the bootstrap-loader module. Then the only additional boilerplate would be a single line of code, something like @BenjaminSchubert @frickt For future reference, what's the simplest addition we could make to https://github.com/shakacode/bootstrap-loader/tree/master/examples to test bootstrap interal dependency issues like this one? |
@Judahmeek I think what @sky-coding wrote is the simplest way of explaining what to do. I'd add it to the docs with the JQuery path. Having to add manually theses plugins is not a problem given that we also have to add jquery manually. |
Exactly the same problem. If necessary, I can add my webpack.config.js This is my .bootstraprc:loglevel: debug
No error while building. Log:bootstrap-loader: Using config file /Users/MYFOLDER/.bootstraprc module.exports.css = require ("style!css!postcss!resolve-url!sass?sourceMap!./lib/bootstrap.styles.loader.js!./no-op.js"); 50% building modules 425/636 modules 211 active ...de_modules/ng2-validators/src/util.jsbootstrap-loader: Scripts output: 42% building modules 431/804 modules 373 active ...ode_modules/bootstrap-loader/no-op.jsbootstrap-loader: Styles output: 20503ms building modules |
@Ks89 check out the post made a few days ago by @sky-coding, his solution resolves the issue.You can check out my webpack.common.js for a reference. |
Thank u. It's working. |
* Add Table of Contents * Addressed Issue #172
@borysn Now that the documentation is updated (see above commit), can we close this issue? |
@Judahmeek everything looks good to me |
@Judahmeek there is a duplicate |
@sky-coding @Andrey-Pavlov @Judahmeek we need some agreement on the preferred solution. I'll release once the 3 of you agree, or if we get more consensus from other community participants. |
@justin808 I didn't realize there was a disagreement. Using Their example shows shimming Compiling from their source should not be an option, if that is the alternative on the table. |
Hey guys!
I'm running into an issue using popovers, seems they are having trouble. Starting up my application shows an error
Uncaught ReferenceError: Tooltip is not defined popover.js?7071:formatted:93
The referenced line of code in the bootstrap file
popover.js
shows...popovers seem to be working fine in alpha 4, so I'm submitting the issue here. Correct me if I'm mistaken, I could be missing something here.
The text was updated successfully, but these errors were encountered: