Partial imports with rollup failing

[hville]

Following up on #45 and on @jshcrowthe's comment:

Use case: just importing the database layer to develop and unit test individual modules that need a common async data store. They will likely eventually be used in the browser but development, unit testing, and packaging is just so much easier and faster in node.

//app.js
import * as firebase from './node_modules/firebase/app'
import './node_modules/firebase/database'
firebase.initializeApp({databaseURL: 'x.y.z'}, 'local').database().goOffline()

1. using rollup in the CLI >rollup -o app.bld.js -f cjs app.js

     'initializeApp' is not exported by 'node_modules\firebase\app.js'
     Use of eval is strongly discouraged, as it poses security risks and may cause issues with minification

2. using rollup in a script with the nodeResolve() and commonjs({include: 'node_modules/**'}) plugins

    'initializeApp' is not exported by 'node_modules\firebase\app.js'

3. Tried importing from ./node_modules/firebase/firebase-app but being build for the browser I get a navigator error in node

4. I also tried many a few combinations directly in the firebase/app/ folder with browserify to get an intermediate build that would be easier to consume but the build system looks like it was hacked to suit babel.

I understand I am trying to use the database component in a way that is not the intended typical use but I thought that if there were less frictions in just using the firebase toolset it would be much easier to get there progressively.

[google-oss-bot]

Hey there! I couldn't figure out what this issue is about, so I've labeled it for a human to triage. Hang tight.

[jsayol]

FYI, it works fine if you change your imports to:

import * as firebase from 'firebase/app';
import 'firebase/database';

[hville]

Hi @jsayol. Could you clarify what rollup plugins and/or settings you are using? If used directly I get 'firebase/app' is imported by app.js, but could not be resolved – treating it as an external dependency. It works but only because firebase never gets bundled at all and the require is left there intact. If I used the rollup resolve plugin and/or the commonjs module I get the same errors listed above.

Here is my environment:

• windows 10
• rollup 0.42.0
• firebase 4.1.2

[anlexN]

i have also some same problem!

[jshcrowthe]

@hville, @anlexN if either of you could provide me a small repo highlighting the issue I'd be happy to take a look.

[anlexN]

@jshcrowthe , can you showcase firebase how to bind rollupjs?

[cspanring]

@jshcrowthe there is an issue filed on the rollup repo, linking a MCVE to reproduce the underlying issue.