![Create React App Officially Deprecated Amid React 19 Compatibility Issues](https://cdn.sanity.io/images/cgdhsj6q/production/04fa08cf844d798abc0e1a6391c129363cc7e2ab-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Create React App Officially Deprecated Amid React 19 Compatibility Issues
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.
exports-test-wintercg
Advanced tools
Module exposing a number of different `exports` fields, for testing which one your bundler/environment ends up using
Just a silly package that implements a whole lot of different exports
entries in package.json
, along with non-standard but often used root-level fields such as module
, browser
etc.
All the exports expose a single named export: getUsedField()
, which returns a string representing which field was used.
This can be useful if you are authoring or consuming packages and want to understand how your environment (node/deno/bundler/cloud) resolves which file to use.
In addition, there is a second path you can import: exports-test/env
, which exposes a getEnvironmentDetails()
method. This returns an object of the following shape:
{
// Globals
process: true,
window: false,
global: true,
globalThis: true,
document: false,
// APIs/methods
require: true,
XMLHttpRequest: false,
EventSource: false,
WebSocket: false,
fetch: true,
setImmediate: true,
URL: true,
URLSearchParams: true,
ReadableStream: true,
WritableStream: true,
Headers: true,
subtleCrypto: true, // crypto.subtle
// Node.js (and similar)
processTitle: 'node', // `process.title`
processVersion: 'v18.0.0', // `process.version`
}
The keys represent the API/global we are checking for, and the value represents whether or not the API is available. It does not do any deep checks, however - this is merely a typeof
check - as long as it is not undefined
, it is treated as being present.
$ npm install exports-test
// ESM / TypeScript
import {getUsedField} from 'exports-test'
import {getEnvironmentDetails} from 'exports-test/env'
// CommonJS
const {getUsedField} = require('exports-test')
const {getEnvironmentDetails} = require('exports-test/env')
getUsedField() // 'exports.node'
getEnvironmentDetails() // {...}
MIT-licensed. See LICENSE.
FAQs
Module exposing a number of different `exports` fields, for testing which one your bundler/environment ends up using
The npm package exports-test-wintercg receives a total of 0 weekly downloads. As such, exports-test-wintercg popularity was classified as not popular.
We found that exports-test-wintercg demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.