Skip to content

Worried by dependency warnings #10

Description

@jgclark

I've just found your project, which looks a great fit for a publishing workflow I have. (I've been trying 'typst', but it's just too opaque for me.)

I've installed 0.5.0.b2, and got the following warnings:

npm install -g pagedjs-cli@0.5.0-beta.2
npm warn deprecated @babel/polyfill@7.12.1: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead
npm warn deprecated puppeteer@22.15.0: < 24.15.0 is no longer supported
npm warn deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

Is it possible for me to upgrade locally to get onto current releases, and avoid security issues? And/or is there a reason for being held on these sometimes quite old dependencies? Thanks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions