Lars Willighagen

I don't know if I've seen any with whitespace, but I do know that just `/` and `.` is not enough for some relatively common DOIs. Some publishers issue DOIs...

Or rollup, I guess...

I personally never use Webpack and I never got around to try making it work yet. However, I think that it should work mostly apart from an issue that should...

> Is the npm package [citation-js](https://www.npmjs.com/package/citation-js) generated from this repository or the new one? Because the link still points to this repository. Should I use @citation-js/core instead? Because https://citation.js.org/ tells...

Hm, I'll have to try that at some point. Apart from that, let me know if I can help.

So by trial and error I found a number of things to improve: 1. rollup seems to work a lot better if `nodeResolve` is the first plugin 2. `Cite` is...

Regarding the first point, `browser: true` is the right way to go but it doesn't get applied because of the order of the plugins.

Okay so if you use `citation-js` instead of `@citation-js/core` you should not use the brackets `import { Cite } ...` but instead what you had before. Sorry for the confusion.

Sounds good. > I am not really sure how you activate the plugin so that you can pass bibtex to the Cite constructor again. Normally this, unless that doesn't work....

A lot of these are converted while rewriting the tests for the new repository: https://github.com/citation-js/citation-js/commit/57ba9ff6ef3bd3220085d1d4847ff951bd4f9242#diff-098f6bcd4621d373cade4e832627b4f6. Only the `core` package tests are still `expect.js`.