Seal.JS

  • Resolved Anonymous User 14978628

    (@anonymized-14978628)


    9 years, 6 months ago

    Just wondering what seal.js is in the exclude list?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Luke Cavanagh

    (@lukecavanagh)

    9 years, 6 months ago

    @martychc23

    I think it is related to this

    Seal can verify that packages installed during development are identical to those installed during deployment. The standard npm shrinkwrap only ensures that package versions are the same, but does not verify contents. seal checks the shasum of the package tarballs downloaded by npm during development and deployment to ensure they are the same.

    https://github.com/zaach/npm-seal/blob/master/lib/seal.js

    https://github.com/futtta/autoptimize/blob/master/classes/autoptimizeConfig.php#L229

    • This reply was modified 9 years, 6 months ago by Luke Cavanagh. Reason: clarify wording
    Plugin Author Frank Goossens

    (@futtta)

    9 years, 6 months ago

    if I remember correctly, seal.js was a 3rd party js thingie used to display a page’s SSL certificate status on thy fly. it needed to excluded because at the time AO moved non-aggregated JS around (it still can, but does not by default any more) and it did a document.write or so.

    that being said, you can safely remove it, I just left it in there as an example 🙂

    frank

    Thread Starter Anonymous User 14978628

    (@anonymized-14978628)

    9 years, 6 months ago

    Thanks guys, i will remove it from the exclude list.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Seal.JS’ is closed to new replies.

  • 3 replies
  • 3 participants
  • Last reply from: Anonymous User 14978628
  • Last activity: 9 years, 6 months ago
  • Status: resolved