Hello! Version 3.1.0. does not work with Vaadin 14.5.3, 14.6.1, 14.7.0alph

Directory pdf-browser
1

Hello!

Version 3.1.0. does not work with Vaadin 14.5.3, 14.6.1, 14.7.0alpha2.

Version 3.0.1 is working.

What is happening? Using “pnpm” and I think “npm” the build of Vaadin UI fails. Somewhere there is a problem building the UI. Switching back to 3.0.1 generates the UI.

It is a little bit spooky. I do not know where the error is.

But I can reproduce the problem by switching the version.

pdf-browser is a good and useful component. Could you invest some time to find the problem? Of course I know. It is a hobby project, not work.

Greetings, Thomas

2

Hi,

I’m not able to reproduce the issue. Can you try removing node_modules, package.*, webpack.*? If that doesn’t help, could you share a minimal project that I can use to reproduce the issue?

3

Hello!

I removed folders and files. Same problem.

Will try to share a project.

Many greetings and stay healthy, Thomas

4

Did you find any other solution? Any other Add-ons that you can recommend? I have a pdf file and I need to open it in a new browser tab, but with this Add-On I couldn’t…all versions of this Add-On for my project, it didn’t work, I use vaadin 14.6.3… I tried versions 3.1.0 - 3.0.1 - 3.0.0 here and nothing made the pdf open

5

I’m not able to reproduce the issue. I’ve tried with different projects and it works. If someone can share a minimal project to reproduce the issue, that’d be great. Otherwise, I’m afraid there’s not much I can do to help.

6

Hello!

Thank you for your help.

I will try to build a small project for my problem. But next day there is too much other work.

I will give feeback.

Thank you very much, Thomas

7

I can confirm that I’ve the same issue, even after a vaadinClean.

In the browser console I see the following error from the generated vaadin-bundle-…cache.js: “Uncaught DOMException: CustomElementRegistry.define: ‘dom-module’ has already been defined as a custom element”

I’ve no experience with such errors, but Google says I should execute “npx find-duplicate-dependencies” in such cases. And this is the output:

> npx find-duplicate-dependencies
This package has the following duplicate dependencies:

@polymer/polymer :
[
  {
    name: '@polymer/polymer',
    version: '3.2.0',
    from: undefined,
    path: 'no-name/@lrnwebcomponents/pdf-browser-viewer/@polymer/paper-button/@polymer/paper-behaviors/@polymer/iron-behaviors'
  },
  {
    name: '@polymer/polymer',
    version: undefined,
    from: undefined,
    path: 'no-name/@lrnwebcomponents/pdf-browser-viewer'
  }
]