jlhwung / hexo-offline Goto Github PK

Version 4.1.3 of babel-plugin-istanbul just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As babel-plugin-istanbul is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 1.5.2 of babel-preset-env just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As babel-preset-env is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

How to pre-cache a cdn path

If a visitor enters an article directly, the article will never be updated until the service worker expires

Expected: The register snippet should be only inserted when public is generated.

There's something that I dont want offline;
I find the issuse here

but config like this wont work

staticFileGlobs: 
- !no-offline/**/*

other regex try !/no-offline/**/*、/!(no-offline)/**/*....

How can I config to ignore some file?

由于 next 主题采用 jquery.fancybox.css?v=2.1.5 这样的链接形式，多了 ?v=2.1.5，造成这种类型的资源无法离线。

查看了 sw-precache 文档，发现只要添加 ignoreUrlParametersMatching 即可。

一番尝试后，只需在 _config.yml 中添加如下部分即可正常离线。

offline:
  # next 主题部分资源以 ?v=2.1.5 引入，此配置用于此配置用于让这类资源生效
  ignoreUrlParametersMatching:
  - /^v$/

希望作者能添加到文档中。

Version 5.2.0 of sw-precache just got published.

This version is covered by your current version range and after updating it in your project the build failed.

sw-precache is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

如果是类似 https://blogs.kainy.cn/2018/07/%E5%8D%9A%E5%AE%A2%EF%BC%8F%E8%B5%84%E8%AE%AF%E7%B1%BB%E7%BD%91%E9%A1%B5%E5%9C%A8%E5%B0%8F%E7%A8%8B%E5%BA%8F%E4%B8%AD%E5%88%86%E4%BA%AB%E7%9A%84%E6%96%B9%E6%A1%88/ 的URL结构，就会导致访问不到sw.js文件。

Version 10.3.3 of tap just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As tap is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

按照说明安装后如下配置：

offline:
  maximumFileSizeToCacheInBytes: 10485760
  staticFileGlobs:
  - public/**/*.{js,html,css,png,jpg,gif,svg,eot,ttf,woff,woff2}
  stripPrefix: public
  verbose: true
  ignoreUrlParametersMatching:
  - /^v$/

然后hexo clean && hexo g后，并没有看到sw的注册的相关脚本在public文件中出现。

When I run hexo g, it generates service-worker.js in my public/ directory. But when I run hexo d, the service-worker.js can't be copied to the .deploy_git, so it doesn't work.

In the generated log of hexo, no INFO Generated: service-worker.js, so I think hexo-offline doesn't follow the convention of hexo to generate file. It just my thought. So I want to know how to solve this.

Version 3.3.1 of hexo just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As hexo is “only” a peerDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

[email protected] /Users/wangqingbin/blog
├── UNMET PEER DEPENDENCY [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

npm ERR! peer dep missing: hexo@^3.2.2, required by [email protected]

能否设置hexo s 不 Caching static resource xxxx资源
而且关闭hexo s 又会在一次 Caching static resource xxxx资源

hexo g 会Caching static resource xxxx资源
hexo d 又会再一次Caching static resource xxxx资源

还有served via CDN
引用了https://cdn.jsdelivr.net/npm/velocity-ui-pack@latest/velocity.ui.min.js

options:
origin: 是写 cdn.jsdelivr.net/npm 还是cdn.jsdelivr.net

我知道

    swSrc: './sw-template.js',
    swDest: './sw.js',

是生成 sw.js的路径但是没有找到 sw.js读取的路径，貌似一直在根目录下读取 sw.js,但是我的 sw.js文件生成在一个子文件夹里了，运行hexo g && hexo s的话一直提醒找到不到 sw.js文件

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency husky to v9

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update actions/cache action to v4
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update coverallsapp/github-action action to v2
• chore(deps): update dependency hexo to v7
• chore(deps): update dependency jest to v29
• chore(deps): update dependency lint-staged to v15
• chore(deps): update dependency prettier to v3
• chore(deps): update dependency rimraf to v5
• fix(deps): update dependency workbox-build to v7
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Version 5.0.1 of cross-env just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As cross-env is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

When I update my website, I can see service worker fetching new content. However, if I refresh, I still see the old content.

Here is my hexo-offline.config.cjs file.

module.exports = {
    globDirectory: "public",
    swDest: "public/service-worker.js",
    globPatterns: [
        "**/*.{js,html,css}",
    ],
    maximumFileSizeToCacheInBytes: 52428800,

    runtimeCaching: [
        {
            urlPattern: /\.(png|jpg|webp|gif|woff|woff2|otf|ttf)/,
            handler: "CacheFirst"
        },
        {
            urlPattern: "*",
            handler: "CacheFirst"
        },
    ]
}

Version 10.4.0 of tap just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As tap is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

When I want to update my site as run hexo clean && hexo d, but the offline resource is long cache so that my site will not update. Only unregister my service workers I can update.

I want to return an offline page instead of system offline page. It seems I need navigateFallback, how can I set this

Process:

1. run hexo-offline with default config
2. open public/index.html

Expect: service-worker registering template snippet is injected only once
Actual: injected for three times

Affected hexo version: 3.3.5
Working hexo version: 3.2.4

Version 3.3.7 of hexo just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As hexo is “only” a peerDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 1.3.0 of babel-preset-env just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As babel-preset-env is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Thank you for a wonderful package. I would like to ask whether this package supports Hexo@^5.

Version 3.2.0 of cross-env just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As cross-env is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 0.1.4 of babel-preset-babili just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As babel-preset-babili is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴