published package is missing commonjs code

Version info

ReactFire: 2.0.0

Other (e.g. Node, browser, operating system) (if applicable): “next”: “9.0.5”, “typescript”: “^3.5.3”

Test case

I just started a new project with next.js and stumbled on this new version of reactfire, I was excited to give it a try but was immediately disappointed by:

/home/[REDACTED]/node_modules/reactfire/index.js:1
export * from './auth';
^^^^^^

SyntaxError: Unexpected token export

So I opened the reactfire package and found that it doesn’t contain commonjs version of source code.

Steps to reproduce

• create a next.js based project with typescript support
• add reactfire and import it in index.tsx

Expected behavior

Package published on npm should contain valid/runnable node.js code.

[jamesdaniels]

@jhuleatt we’ll want to build for more than one target before publish. I’ll build that into the pipeline.

[shawnmmatthews]

Just as a heads up for anyone that comes across this prior to the update being available. I’ve been able to get this working by building reactfire using “module”: “commonjs” in the tsconfig.json file, and then running the context provider from within a module with ssr: false enabled in Next.