This message was deleted.

Sure.

require

"simply" returns a promise, so we can use JS's promise tools to work with it. Assuming

unpkg

is returning an error, you can catch it and swap in the other provider

P5 = require('<https://unpkg.com/p5@1.2.0/lib/p5.js').catch(()> => require("<https://cdnjs.cloudflare.com/ajax/libs/p5.js/1.6.0/p5.js>"))

You are faster and more elegant. I arrived at the same only after lots of code and using two cells (one to define the function and one to call it):

evalP5 = () => {
  let message = '';
  try {
    require('<https://unpkg.com/p5@1.2.0/lib/p5.js>');
    message = 'p5.js loaded successfully.';
    return require('<https://unpkg.com/p5@1.2.0/lib/p5.js>')
  } catch (error) {
    console.log('Failed to load p5.js from <http://unpkg.com|unpkg.com>. Trying cdnjs.com...');
    try {
      require('<https://cdnjs.cloudflare.com/ajax/libs/p5.js/1.6.0/p5.js>');
      message = 'p5.js loaded successfully.';
      return require('<https://cdnjs.cloudflare.com/ajax/libs/p5.js/1.6.0/p5.js>')
    } catch (error) {
      console.error('Failed to load p5.js from <http://cdnjs.com|cdnjs.com>:', error);
      message = "nothing's working";
      return message;
    }
  }
}

Oh, heads up. I notice that in both my example and Brett's original, the versions of p5.js are different (1.2 in the unpkg branch vs 1.6 in the fallback). It would be best to use the same fixed version

You can just drop the host to have it fall back to cdn.observableusercontent.com:

require('p5@1.2.0/lib/p5.js')

So I could just have catches all the way down.

P5 = require('<https://unpkg.com/p5@1.6.0/lib/p5.js').catch(()> => require("<https://cdnjs.cloudflare.com/ajax/libs/p5.js/1.6.0/p5.js>")).catch(() => require("<https://cdn.jsdelivr.net/npm/p5@1.6.0/lib/p5.min.js>"))

please don't 🙂 just use jsdelivr or leave the host off

if the hosts off will it try different hosts until if gets a win?

until now i didn't even realize that "digital prepping" can exist 😬

ok thanks

@aaronkyle those outages in the first link are reported for data.jsdelivr.com

i realized the first link wasn't great and found the actual status report after. i was curious.

yeah, tbh i wouldn't trust that site (the first one)

I just commented on https://observablehq.com/@tmcw/p5 with a request to update the link as this is the main way people access p5 on observable.