ES6 Module import snippets

es6-export-default.sublime-snippet

<snippet>
	<content><![CDATA[
export default ${1:this}
]]></content>
	<!-- Optional: Set a tabTrigger to define how to trigger the snippet -->
	<tabTrigger>exp</tabTrigger>
	<!-- Optional: Set a scope to limit where the snippet will trigger -->
	<!-- <scope>source.python</scope> -->
</snippet>

es6-export.sublime-snippet

<snippet>
	<content><![CDATA[
export { ${1:this} }
]]></content>
	<!-- Optional: Set a tabTrigger to define how to trigger the snippet -->
	<tabTrigger>exp{</tabTrigger>
	<!-- Optional: Set a scope to limit where the snippet will trigger -->
	<!-- <scope>source.python</scope> -->
</snippet>

es6-import-default.sublime-snippet

<snippet>
	<content><![CDATA[
import ${1:this} from '${2:snippet}';
]]></content>
	<!-- Optional: Set a tabTrigger to define how to trigger the snippet -->
	<tabTrigger>imp</tabTrigger>
	<!-- Optional: Set a scope to limit where the snippet will trigger -->
	<!-- <scope>source.python</scope> -->
</snippet>

es6-import.sublime-snippet

<snippet>
	<content><![CDATA[
import { ${1:this} } from '${2:snippet}';
]]></content>
	<!-- Optional: Set a tabTrigger to define how to trigger the snippet -->
	<tabTrigger>imp{</tabTrigger>
	<!-- Optional: Set a scope to limit where the snippet will trigger -->
	<!-- <scope>source.python</scope> -->
</snippet>

These are very handy. I think both of the export ones could use a ; at the end by default perhaps.