Skip to content
Snippets Groups Projects
Select Git revision
  • 6ed73f69c753d3acc6f68df605498948313385e5
  • main default protected
  • renovate/lock-file-maintenance
  • demo protected
  • person-select-custom
  • dbp-translation-component
  • icon-set-mapping
  • port-i18next-parser
  • remove-sentry
  • favorites-and-recent-files
  • revert-6c632dc6
  • lit2
  • advertisement
  • wc-part
  • automagic
  • publish
  • wip-cleanup
  • demo-file-handling
18 results

rollup.utils.js

Blame
    • Reiter, Christoph's avatar
      68a87639
      Use the rollup resolve plugin for finding package asssets · 68a87639
      Reiter, Christoph authored
      Instead of hardcoding the paths of the node_modules directory we use the node-resolve
      plugin of rollup to find the root of the corresponding JS package and calcucate a path from
      there.
      
      Resolving a package requires calling an async function, so we have to use await in the rollup config.
      Luckily rollup supports configs wrapped in a promise, so we just have to wrap it in a function which returns
      a promise.
      68a87639
      History
      Use the rollup resolve plugin for finding package asssets
      Reiter, Christoph authored
      Instead of hardcoding the paths of the node_modules directory we use the node-resolve
      plugin of rollup to find the root of the corresponding JS package and calcucate a path from
      there.
      
      Resolving a package requires calling an async function, so we have to use await in the rollup config.
      Luckily rollup supports configs wrapped in a promise, so we just have to wrap it in a function which returns
      a promise.
    demo.js 31 B
    import './dbp-common-demo.js';