published package is missing commonjs code

[whollacsek]

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.

[jhuleatt]

@jamesdaniels our current tsconfig outputs esnext:

reactfire/reactfire/tsconfig.json

Line 4 in 803159c

"module": "esnext",

Is fixing this as simple as changing the config to UMD?

[jamesdaniels]

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

[shawnmmatthews]

Is this issue specific to projects using Typescript or any SSR setup? I'm running a very standard JS based NextJS site and just attempted to add FirebaseAppProvider, and I immediately receive the token error. I see that @jamesdaniels is working on solution in the pipeline. Is there a current work around in the meantime? Thanks again for the awesome project.

[peterdeepsix]

I would be willing to put in sometime for PR regarding this issue. @jamesdaniels Let me know if you need any help

[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.