Closed natorojr closed 8 years ago
Note: My last comment wasn't valid...
Alternatively, you can upgrade your package to Babel 6.
... since doing so, without actually removing .babelrc
from your package, could conceivably break people still using Babel 5 (which I think there are still many).
Therefore, the best option for everyone is to add the files
prop to package.json (effectively excluding .babelrc
from your npm distribution) and republishing the package.
I submitted PR #24
I recently upgraded to Babel 6 and noticed the following issues w/ your npm package:
It's generally considered bad practice to publish .babelrc as part of your npm packages. Instead, you should be using the
files
attribute in your package.json (https://docs.npmjs.com/files/package.json#files).Alternatively, you can upgrade your package to Babel 6.