Bangle and NFC

From the documentation, I discovered that the bangle is able to interact with NFC.
So I tried very simple code :

NRF.nfcURL("http://espruino.com");
NRF.on('NFCon', function() { console.log('nfc on'); });
NRF.on('NFCoff', function() { console.log('nfc off'); });

Nothing happen with my phone (Pixel 3a XL)
I tried with NFC Tool app and still nothing
I also used a tiny NFC tag embedded in a little purple rabbit, but even the cuteness effect did not trigger anything.

Am I doing something wrong?

I don't think NFC is supported in bangle. iirc the chip does support it, but the necessary additional hardware is missing.
It is in the firmware as some other espruino devices have it.

...yep, the antenna (and adaption caps) are absent and the NFC pins could be used as plain GPIO for something else. I'm surprised that you do not get errors because according to the list of libraries in the build, NFC library is not included in the list of libs (see bangleJS https://github.com/espruino/Espruino/blob/master/boards/BANGLEJS.py#L28 vs pixleJS https://github.com/espruino/Espruino/blob/master/boards/PIXLJS.py#L30)

The documentation is a bit misleading in that case:
https://www.espruino.com/Reference#t_l_NRF_NFCon

Note: This is only available in NRF52 devices (like Puck.js, Pixl.js, Bangle.js and MDBT42Q) and ESP32 boards

@allObjects I have no errors, I used the espruino ide web page if that matter.

The NRF object has both bluetooth and NFC functionality see header jswrap_bluetooth.h -
https://github.com/espruino/Espruino/blob/master/libs/bluetooth/jswrap_bluetooth.h#L88

Maybe there could be some #ifdef to not include those NFC methods at all. In fact it is almost like that already and the methods are still there but empty, see
https://github.com/espruino/Espruino/blob/master/libs/bluetooth/jswrap_bluetooth.c#L2026
there is check for USE_NFC making the method to do nothing. So not sure why not to remove whole method, I think in other cases methods are removed from same object based on build flags.

Yes, that's true - this should be removed from the build. I'll see about doing that now...

Just sorted.