Add explicit check for importing remote Bootstrap JS

[TimOliver]

G'day Paul! Hope you've been well since try! Swift this year! 👋

I'm in the middle of migrating my blog away from WordPress (at long long last) and I'm looking at redoing the whole lot on Ignite! The documentation and the examples have made it incredibly easy to get started. 🤩

That being said, in typical developer fashion, I'd like to be able to start with an absolutely clean slate so I can specify my own CSS and JS from scratch. I was looking at disabling Bootstrap entirely, and I noticed that even if I set useDefaultBootstrapURLs to .none, it would still remotely import the Bootstrap JS file, which might not be the intended logic here.

Here's a quick PR for adding an explicit check, which I've confirmed already works correctly.

Meanwhile, I'm still looking into if there's already a way to do this, but I'd also like to disable ignite-core.min.css so I can implement my own CSS reset logic. I'll look into that for a separate PR.

Hope this helps! Thanks so much!

[twostraws]

Things have been frantic nonstop here, I'm afraid; so many things are pulling me in so many directions, and I can't see any sort of end in sight 😴 I hope things are a bit quieter there!

You're quite correct with this PR – thank you! And finding a way to detach Bootstrap completely would be great. Obviously it's then on you to make sure something happens for the various classes Ignite looks for, but it sounds like you're ready for that challenge 🙂

[TimOliver]

Haha I know the feeling. I was trying to start my blog migration in January this year and this is the fastest I can go. 😅 Yeah! It's a peaceful summer over here now! Hopefully you and your family can come visit again soon!

No worries! Oh yeah, thanks for the heads-up. I'll see if I end up needing to reimplement any Ignite specific CSS then.

Thanks again Paul!