Originally created by @uzzy-buzzy on GitHub (Sep 14, 2025).
A lot of the repos here are unmaintained, it would be nice to have some sort of indicator for that
Originally created by @uzzy-buzzy on GitHub (Sep 14, 2025).
A lot of the repos here are unmaintained, it would be nice to have some sort of indicator for that
@tvorogec2009-code commented on GitHub (Oct 10, 2025):
import memoize from '@github/memoize'
import {getEnv} from '@github-ui/client-env'
import {IS_SERVER} from '@github-ui/ssr-utils'
import type {JSFeatureFlag} from './client-feature-flags'
function getEnabledFeaturesSet() {
return new Set(getEnv().featureFlags as JSFeatureFlag[])
}
more information on useFeatureFlag and add_client_feature_flag.
*/
export function isFeatureEnabled(name: JSFeatureFlag): boolean {
return featuresSet().has(name)
}
// exported to allow mocking in tests
const featureFlag = {isFeatureEnabled}
export {featureFlag}
function isStorybook() {
try {
return process?.env?.STORYBOOK === 'true' || process?.env?.APP_ENV === 'storybook'
} catch {
return false
}
} In our code that we are doing here, an error occurs try {
return process?.env?.STORYBOOK === 'true' || process?.env?.APP_ENV === 'storybook'
} catch {
return false
} it says that something went wrong and that's why it doesn't work, your task will be to rewrite the code and make it work, then I can upload it to the page.
@tvorogec2009-code commented on GitHub (Oct 10, 2025):
import memoize from '@github/memoize'
import {getEnv} from '@github-ui/client-env'
import {IS_SERVER} from '@github-ui/ssr-utils'
import type {JSFeatureFlag} from './client-feature-flags'
function getEnabledFeaturesSet() {
return new Set(getEnv().featureFlags as JSFeatureFlag[])
}
const featuresSet =
IS_SERVER || process.env.NODE_ENV === 'test' || isStorybook() ? getEnabledFeaturesSet : memoize(getEnabledFeaturesSet)
export function getEnabledFeatures(): JSFeatureFlag[] {
return Array.from(featuresSet())
}
/**
* This function accesses feature flag states which have been loaded into the client env via the `client-feature-flags.ts` file.
* See https://thehub.github.com/epd/engineering/products-and-services/dotcom/features/feature-flags/typescript-frontend
* for more details.
*
* If you're trying to check a feature flag that was added to the `enabled_features` of a React payload via `add_client_feature_flag` in a
* Rails controller, you should use the `useFeatureFlag` hook (from `@github-ui/react-core/use-feature-flag`) instead to access the feature flag state.
* https://thehub.github.com/epd/engineering/products-and-services/dotcom/features/feature-flags/typescript-frontend has
* more information on `useFeatureFlag` and `add_client_feature_flag`.
*/
export function isFeatureEnabled(name: JSFeatureFlag): boolean {
return featuresSet().has(name)
}
// exported to allow mocking in tests
const featureFlag = {isFeatureEnabled}
export {featureFlag}
function isStorybook() {
try {
return process?.env?.STORYBOOK === 'true' || process?.env?.APP_ENV === 'storybook'
} catch {
return false
}
} In our code that we are doing here, an error occurs try {
return process?.env?.STORYBOOK === 'true' || process?.env?.APP_ENV === 'storybook'
} catch {
return false
} it says that something went wrong and that's why it doesn't work, your task will be to rewrite the code and make it work, then I can upload it to the page.
@rubydagrim commented on GitHub (Oct 11, 2025):
Seriously what share the
B•Gresham
On Fri, Oct 10, 2025 at 5:08 AM tvorogec2009-code ***@***.***>
wrote:
> *tvorogec2009-code* left a comment (sindresorhus/awesome#3642)
> <https://github.com/sindresorhus/awesome/issues/3642#issuecomment-3389183614>
>
> Where and what repositories.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/sindresorhus/awesome/issues/3642#issuecomment-3389183614>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BYQKTRMMEH2QWMWG7DZUSZ33W6AR3AVCNFSM6AAAAACGOSD24WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOBZGE4DGNRRGQ>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @uzzy-buzzy on GitHub (Sep 14, 2025).
A lot of the repos here are unmaintained, it would be nice to have some sort of indicator for that
@tvorogec2009-code commented on GitHub (Oct 10, 2025):
import memoize from '@github/memoize'
import {getEnv} from '@github-ui/client-env'
import {IS_SERVER} from '@github-ui/ssr-utils'
import type {JSFeatureFlag} from './client-feature-flags'
function getEnabledFeaturesSet() {
return new Set(getEnv().featureFlags as JSFeatureFlag[])
}
const featuresSet =
IS_SERVER || process.env.NODE_ENV === 'test' || isStorybook() ? getEnabledFeaturesSet : memoize(getEnabledFeaturesSet)
export function getEnabledFeatures(): JSFeatureFlag[] {
return Array.from(featuresSet())
}
/**
client-feature-flags.tsfile.enabled_featuresof a React payload viaadd_client_feature_flagin auseFeatureFlaghook (from@github-ui/react-core/use-feature-flag) instead to access the feature flag state.useFeatureFlagandadd_client_feature_flag.*/
export function isFeatureEnabled(name: JSFeatureFlag): boolean {
return featuresSet().has(name)
}
// exported to allow mocking in tests
const featureFlag = {isFeatureEnabled}
export {featureFlag}
function isStorybook() {
try {
return process?.env?.STORYBOOK === 'true' || process?.env?.APP_ENV === 'storybook'
} catch {
return false
}
} In our code that we are doing here, an error occurs try {
return process?.env?.STORYBOOK === 'true' || process?.env?.APP_ENV === 'storybook'
} catch {
return false
} it says that something went wrong and that's why it doesn't work, your task will be to rewrite the code and make it work, then I can upload it to the page.
@tvorogec2009-code commented on GitHub (Oct 10, 2025):
Where and what repositories.
@rubydagrim commented on GitHub (Oct 11, 2025):
Seriously what share the
B•Gresham
On Fri, Oct 10, 2025 at 5:08 AM tvorogec2009-code @.***>
wrote:
@uzzy-buzzy commented on GitHub (Oct 14, 2025):
@tvorogec2009-code sorry but I have no clue what u just said
@yahyagokmen51-ship-it commented on GitHub (Oct 30, 2025):
<html> <head> <script> function myFunction() { document.getElementById("demo").innerHTML = "slm; } </script> </head>Script in head tag
nbr
Try it </html> <html lang="tr"> <head> <style> body { display: flex; flex-direction: column; justify-content: center; align-items: center; height: 100vh; margin: 0; /* Renkli Arka Plan */ background: linear-gradient(135deg, #ff9a9e 0%, #fad0c4 100%); font-family: 'Segoe UI', Tahoma, Geneva, Verdana, sans-serif; text-align: center; overflow: hidden; } #soru { font-size: 2.5em; margin-bottom: 40px; color: #444; text-shadow: 1px 1px 2px rgba(255, 255, 255, 0.5); z-index: 1; } #resim { /* Eğer resim kullanmak isterseniz bu kısmı açabilirsiniz */ /* margin-bottom: 30px; width: 80%; max-width: 500px; border-radius: 10px; box-shadow: 0 4px 10px rgba(0, 0, 0, 0.2); z-index: 1; */ display: none; /* Bu örnekte resmi gizledik, isterseniz kaldırabilirsiniz */ } .cevap-butonu { padding: 15px 30px; margin: 10px; font-size: 1.3em; cursor: pointer; border: 2px solid #fff; border-radius: 50px; /* Yuvarlak butonlar */ transition: all 0.3s ease; font-weight: bold; box-shadow: 0 5px 15px rgba(0, 0, 0, 0.2); z-index: 100; } #evetBtn { background-color: #00b894; /* Turkuaz/Canlı Yeşil */ color: white; } #evetBtn:hover { transform: scale(1.05); background-color: #00a082; } #hayirBtn { background-color: #ff6b6b; /* Canlı Kırmızı */ color: white; position: absolute; /* Yer değiştirme için mutlak konumlandırma */ transition: transform 0.1s ease-out; /* Hızlı hareket */ } #mesaj-alani { position: fixed; top: 0; left: 0; width: 95%; height: 100%; display: none; flex-direction: column; justify-content: center; align-items: center; background-color: rgba(255, 255, 255, 0.95); /* Yarı saydam beyaz */ z-index: 999; } #sonMesaj { font-size: 3em; color: #e84393; /* Canlı Pembe */ text-align: center; padding: 20px; border-radius: 15px; background-color: #fff; box-shadow: 0 0 30px rgba(255, 105, 180, 0.6); animation: bounceIn 1s forwards; }@nalkarsuyash5 commented on GitHub (Oct 30, 2025):
Hii