npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

webpack-fix-default-import-plugin

v1.0.3

Published

Webpack plugin to fix default import for non ES6 modules

Downloads

4,506

Readme

Webpack Fix Default Import Plugin

Why?

With Babel transpiler you could write:

import React from 'react';
import ReactDOM from 'react-dom';

In this case Babel will be able to resolve module.exports.default as modules.exports if module.exports.default is not defined.

It doesn't work with TypeScript compiler which targets ES5, so we have to use:

import * as React from 'react';
import * as ReactDOM from 'react-dom';

One well know workaround for this issue is to use TWO transpilers, typescript first targeted to ES6 and Babel second targeted to ES5. Extra transpilation takes more time and break source maps.

The other solution is to hook into webpack's require() implementation and polyfill module.exports.default if it is blank and module is not ES6 module.

This plugin hooks into require() and try to polyfill module.exports.default.

Installation

npm install --save-dev webpack-fix-default-import-plugin

webpack.config.js example:

var FixDefaultImportPlugin = require('webpack-fix-default-import-plugin');

module.exports = {
  ...
  plugins: [
    ...
    new FixDefaultImportPlugin()
  ],
};

tsconfig.json example:

{
  "compilerOptions": {
    "sourceMap": true,
    "noImplicitAny": true,
    "noEmitHelpers": true,
    "allowSyntheticDefaultImports": true,   // required
    "module": "commonjs",                   // required
    "target": "es5",                        // required
    "jsx": "react"
  },
  "exclude": [
    "node_modules",
    "typings/globals"
  ]
}

tslint.json example:

{
  ...
  "rules": {
    ...
    "no-unused-variable": [true, {"ignore-pattern": "^(React|ReactDOM)$"}],
    "import-name": false,
    "no-default-export": false
  }
}