Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[bug] ssr-shims.js uses deprecated globalThis.litSsrCallConnectedCallback

未关闭
#3,158 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@zeroedin 已经在做这个了。

开始于 2026年8月6日。

评估

这个 Issue 还没有评估数据。

描述

bug

Summary

@patternfly/pfe-core/ssr-shims.js sets globalThis.litSsrCallConnectedCallback = true to opt elements into connectedCallback during Lit SSR. This global was deprecated in @lit-labs/[email protected] in favor of LitElementRenderer.renderOptions.

The result is a repeated console warning during every SSR render pass:

litSsrCallConnectedCallback is deprecated. Please use LitElementRenderer.renderOptions instead.

Current behavior

https://github.com/patternfly/patternfly-elements/blob/main/core/pfe-core/ssr-shims.ts

globalThis.litSsrCallConnectedCallback = true;

This triggers the deprecation path inside LitElementRenderer.connectedCallback() on every element instance rendered, flooding build logs with warnings.

Expected behavior

Replace the deprecated global with the new per-element configuration API:

import { LitElementRenderer } from '@lit-labs/ssr/lib/lit-element-renderer.js';

// Replicate the previous blanket opt-in for PFE/RHDS elements
LitElementRenderer.renderOptions.push(
  (element) =>
    element.localName.startsWith('pf-') || element.localName.startsWith('rh-')
      ? { connectedCallback: true }
      : undefined
);

Or, to preserve the exact previous behavior (all LitElements get connectedCallback called):

LitElementRenderer.renderOptions.push(() => ({ connectedCallback: true }));

Impact

  • The warning is cosmetic for now — @lit-labs/ssr still honors the global alongside the warning.
  • However, a future major version of @lit-labs/ssr will likely remove support for the global entirely, making this a future breaking change.

Environment

  • @patternfly/pfe-core: 5.0.8
  • @lit-labs/ssr: 4.1.0
主要语言
TypeScript
星标
394
派生
107
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

patternfly/patternfly-elements 的其他 Issue

查看 patternfly/patternfly-elements 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。