Why Is `Export Default Const` invalid?


Why Is `Export Default Const` invalid?

I see that the following is fine:
const Tab = connect( mapState, mapDispatch )( Tabs );
export default Tab;

However, this is incorrect:
export default const Tab = connect( mapState, mapDispatch )( Tabs );

Yet this is fine:
export default Tab = connect( mapState, mapDispatch )( Tabs );

Can this be explained please why const is invalid with export default? Is it an unnecessary addition & anything declared as export default is presumed a const or such?


Solution 1:

const is like let, it is a LexicalDeclaration (VariableStatement, Declaration) used to define an identifier in your block.

You are trying to mix this with the default keyword, which expects a HoistableDeclaration, ClassDeclaration or AssignmentExpression to follow it.

Therefore it is a SyntaxError.

If you want to const something you need to provide the identifier and not use default.

export by itself accepts a VariableStatement or Declaration to it’s right.

AFAIK the export in itself should not add anything to your current scope.

The following is fineexport default Tab;

Tab becomes an AssignmentExpression as it’s given the name default ?

export default Tab = connect( mapState, mapDispatch )( Tabs ); is fine

Here Tab = connect( mapState, mapDispatch )( Tabs ); is an AssignmentExpression.

Solution 2:

You can also do something like this if you want to export default a const/let, instead of

const MyComponent = ({ attr1, attr2 }) => (<p>Now Export On other Line</p>);
export default MyComponent

You can do something like this, which I do not like personally.

let MyComponent;
export default MyComponent = ({ }) => (<p>Now Export On SameLine</p>);

Solution 3:

If the component name is explained in the file name MyComponent.js, just don’t name the component, keeps code slim.

import React from 'react'

export default (props) =>
    <div id='static-page-template'>

Solution 4:

Paul’s answer is the one you’re looking for. However, as a practical matter, I think you may be interested in the pattern I’ve been using in my own React+Redux apps.

Here’s a stripped-down example from one of my routes, showing how you can define your component and export it as default with a single statement:

import React from 'react';
import { connect } from 'react-redux';

@connect((state, props) => ({
    appVersion: state.appVersion
    // other scene props, calculated from app state & route props
export default class SceneName extends React.Component { /* ... */ }

(Note: I use the term “Scene” for the top-level component of any route).

I hope this is helpful. I think it’s much cleaner-looking than the conventional connect( mapState, mapDispatch )( BareComponent )

Solution 5:

The answer shared by Paul is the best one. To expand more,

There can be only one default export per file. Whereas there can be more than one const exports. The default variable can be imported with any name, whereas const variable can be imported with any name.

var message2 = ‘I am exported’;

export default message2;

export const message = ‘I am also exported’

At the imports side we need to import it like this:

import { message } from ‘./test’;


import message from ‘./test’;

With the first import, the const variable is imported whereas, with the second one, the default one will be imported.