Solidity – Counters.Counter vs totalSupply in OpenZeppelin Contracts

I see good observations about style but I didn't see the safety aspect.

Setting a variable to private ensures that it can only be manipulated via functions in the contract designed for that purpose and never by a successor contract that inherited it.

That means an errant contract could not accidentally zero out, say, owner ... a potentially disastrous accident that is preventable with private.

So, it's worth considering for vital state elements.

Hope it helps.

UPDATE

    pragma solidity 0.4.25;
    
    contract Risky {
        
        string public vital;
        
        constructor() public {
            vital = "do not change";
        }
    }
    
    contract Careless is Risky {
        
        function oops() public {
            
            /*
            Since vital is "public", this child contract is free to write to it.
            This is not ideal because it could lead to critical values overwritten.
            This child contract is free to make mistakes that could be disasterous.
            */
            
            vital = "game over";
        }
    }
    
    /*
    ----------------------------------------
    Using private for safety
    ----------------------------------------
    */
    
    contract Cautious {
        
        string private vital;
        
        constructor() public {
            vital = "cannot be changed by accident";
        }
        
        function getVital() public view returns(string) {
            return vital;
        }
        
        function setVital(string youKnowWhatYoureDoing) public {
            vital = youKnowWhatYoureDoing;
        }
    }
    
    contract Isolated is Cautious {
        
        /* 
        This child cannot stomp on Cautious' "vital" even if it wants to because it's not "public" or "internal". 
        It *must* use Cautious' getter and setter functions which means Cautious is in control. 
        */
        
    }

Ran into this myself as well. Are you using ethers.js with Buidler?

The safeTransferFrom method is overloaded and generally with ethers.js the bare definition is the default method used.

If you run console.log( Object.keys(token) ) you'll see the methods on the token and you'll likely see two definitions of safeTransferFrom. Pick the one you want to use then you can call it like this:

token['safeTransferFrom(address,address,uint256)'](fromAddr, toAddr, tokenId);