SOLID Principles in JavaScript

class Bird {
  fly() {
    console.log('Flying...');
  }
}

class Penguin extends Bird {
  fly() {
    throw new Error('Penguins cannot fly!');
  }
}

The code is too simple
Bird should not have a fly method
Penguin violates the contract established by its base class
This code violates the Liskov Substitution Principle (LSP) because Penguin, despite being a subclass of Bird, cannot fulfill the contract established by its base class. LSP states that objects of a superclass should be replaceable with objects of its subclasses without breaking the application. A better design would be to have separate interfaces like FlyingBird and NonFlyingBird, or to model the behavior differently.
The error message is not descriptive enough