Record, Object, and List View Navigation

this[NavigationMixin.Navigate]({
    type: 'standard__recordPage',
    attributes: {
        recordId: this.accountId,
        objectApiName: 'Account',
        actionName: 'view', // or 'edit', or 'clone'
    },
});

standard__recordPage navigates to a specific record. actionName determines whether it opens in view, edit, or clone mode.

this[NavigationMixin.Navigate]({
    type: 'standard__objectPage',
    attributes: {
        objectApiName: 'Contact',
        actionName: 'home', // or 'new'
    },
});

standard__objectPage navigates to a whole object's page rather than one specific record — actionName: 'home' for the object's default list view landing page, or 'new' to open the new-record form directly.

this[NavigationMixin.Navigate]({
    type: 'standard__objectPage',
    attributes: {
        objectApiName: 'Opportunity',
        actionName: 'list',
    },
    state: {
        filterName: 'Recently Viewed',
    },
});

Still standard__objectPage, but with actionName: 'list' and a state.filterName naming the specific list view to open.

Custom components very often need to send the user somewhere else in the org after an action completes — opening the record that was just created, or taking them back to a relevant list view. Getting the right type/actionName combination is a common, very practical need.