Those modules are built-in, and this usually happens if the CLI hasn't been able to work out what type of board is connected (it queries process.env when it connects) so it doesn't know that the libraries are actually built in.

There was a bug in the order in which the CLI did things that messed this up, but I thought that was fixed - it's entirely possible I haven't updated it in NPM though, and I'll try and do that today.

NPM, installed last night. I made the obvious realisation they were built-in shortly after posting, but locked the thread by accident. This is what happens when I try to code late at night while on heavy medication! :)