fix: set up non-default ipx providers if options.ipx is set#1618
Conversation
Previously, specifying a custom provider would prevent setup of ipx
Co-authored-by: Daniel Roe <daniel@roe.dev>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1618 +/- ##
==========================================
- Coverage 62.93% 62.83% -0.10%
==========================================
Files 79 79
Lines 3529 3536 +7
Branches 407 411 +4
==========================================
+ Hits 2221 2222 +1
- Misses 1279 1285 +6
Partials 29 29 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Pushed a slight refactor - does that still work for you? |
|
Seems fine? I couldn't quite figure out what ipxStatic did or make it work myself — though it does seem to require the ipx initialization, so if you wanted to use it alongside another default, your change would make it impossible. |
|
|
ipx providers
ipx providersipx providers if options.ipx is set
|
Fix #1676 |
Fixes #1414
❓ Type of change
📚 Description
Previously, specifying a custom provider would prevent setup of ipx, which happens in a
'nitro:inithook. That is, there was no way use ipx if it wasn't your default provider.Now, you just need to add
ipxto the image options: