Skip to content

uncaught reference in 4.11 #1057

Closed
Closed

Description

@akhmerov

Bug Report

When using the freshly released version 4.11 I observe that the library doesn't load and the problem seems to be on the docsify side.

image

Steps to reproduce

Use index.html like this one

What is current behaviour

docsify doesn't load

What is the expected behaviour

docsify loads :)

Other relevant information

  • Bug does still occur when all/other plugins are disabled?

  • Your OS: Ubuntu

  • Browser version: chrome Version 80.0.3987.132 (Official Build) (64-bit)

  • Docsify version: 4.11

  • Docsify plugins: docsify-katex (but the problem appears also without it).

Activity

  1. anikethsaha commented on Mar 9, 2020

    @anikethsaha
    Member

    ohh shoot !
    Please use 4.10.2
    I will fix it now . Something wrong with rollup config

  2. akhmerov commented on Mar 9, 2020

    @akhmerov
    Author

    Yeah, I pinned 4.10.2, sure, no problem.

  3. vardaro commented on Mar 9, 2020

    @vardaro

    Wow you guys are fast!

  4. anikethsaha commented on Mar 9, 2020

    @anikethsaha
    Member

    if anyone can help with this rollup issue .

    image

    Thanks

  5. slikts commented on Mar 9, 2020

    @slikts

    There shouldn't be untested releases; the default setup doesn't pin the version, so every site that uses it is now broken. It's also why the default template should include a fallback link.

    Pinned location: //unpkg.com/docsify@4.10.2/lib/docsify.min.js

  6. anikethsaha commented on Mar 9, 2020

    @anikethsaha
    Member

    released v4.11.1
    Please confirm if there are any issues or not

  7. xuqingkuang commented on Mar 9, 2020

    @xuqingkuang

    if anyone can help with this rollup issue .

    image

    Thanks

    Try to execute npm ls css.escape, to make sure the css.escape is installed?

    I tested to build the docsify, the css.escape was built correctly.

  8. slikts commented on Mar 9, 2020

    @slikts

    v4.11.1 appears to work, thanks for the fix, but please add automated testing to the process.

  9. anikethsaha commented on Mar 9, 2020

    @anikethsaha
    Member

    v4.11.1 appears to work, thanks for the fix, but please add automated testing to the process.

    We do have some e2e tests but they are not so strong and not many!
    I am not so into testing so I couldn't able to write strong tests.
    So I request community to help with strong tests!

  10. anikethsaha commented on Mar 9, 2020

    @anikethsaha
    Member

    Closing as its been fix.
    Please open new issue if any other issue is there

  11. jeffin143 commented on Mar 9, 2020

    @jeffin143

    v4.11.1 appears to work, thanks for the fix, but please add automated testing to the process.

    We do have some e2e tests but they are not so strong and not many!
    I am not so into testing so I couldn't able to write strong tests.
    So I request community to help with strong tests!

    I will be there from next weekend to help :)

    Great work anyways

  12. anikethsaha commented on Mar 9, 2020

    @anikethsaha
    Member

    v4.11.1 appears to work, thanks for the fix, but please add automated testing to the process.

    We do have some e2e tests but they are not so strong and not many!
    I am not so into testing so I couldn't able to write strong tests.
    So I request community to help with strong tests!

    I will be there from next weekend to help :)

    Great work anyways

    🎉

    Thanks

  13. trusktr commented on Jun 7, 2020

    @trusktr
    Member

    Just FYI the new unit tests in #1189 should catch any instance of the script not loading.

  14. anikethsaha commented on Jun 7, 2020

    @anikethsaha
    Member

    will it catch while running in development mode ? cause this issue occurred after running the build and ignoring the warning of rollup.

  15. trusktr commented on Jun 7, 2020

    @trusktr
    Member

    Oh wait, actually the test script currently tests whatever build you last made. I will update test to test specifically the prod build.

    EDIT: Oh wait, pull request #1189 does already test the production script. I added comments to the PR to explain it.

  16. anikethsaha commented on Jun 7, 2020

    @anikethsaha
    Member

    Oh wait, actually the test script currently tests whatever build you last made. I will update test to test specifically the prod build.

    Post build tests ? worth it though, may be in a separate PR ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions