gireeshpunathil
commented
3 weeks ago Re-evaluate the benefits of the feature. Decide whether to remove the feature entirely or delegate its maintenance to a team.
- may be, we could also assess where does the feature stand in terms of its progress towards stability, what are the gaps and what are the opportunities?
- may be, we could also assess where does the feature stand in terms of field adoption, what are the use cases and what the users think of about it?
RafaelGSS
BridgeAR
GeoffreyBooth
ronag
mcollina
Qard
anonrig
joyeecheung
marco-ippolito
I believe it's time to discuss our policies around experimental features in the project. Features like
--experimental-network-importare challenging to assess and maintain, especially when there is no active champion or creator overseeing them.Proposal
I propose that when the creator or champion of an experimental feature becomes inactive, we should:
This approach will help us set clear expectations, assess and review vulnerabilities, and ensure better maintenance of our experimental features.
Recent Example
We recently dropped the
--experimental-policyfeature because:Actionable Steps
To facilitate this discussion, I have written a simple script to list all experimental APIs from
nodejs/node/docs/api/**. You can find it here.Can we evaluate these experimental features either asynchronously or through a dedicated call?
AsyncLocalStorage.bind(fn)AsyncLocalStorage.snapshot()asyncLocalStorage.disable()asyncLocalStorage.enterWith(store)asyncLocalStorage.exit(callback[, ...args])AsyncHooksbuffer.resolveObjectURL(id)subprocess[Symbol.dispose]()--allow-addons--allow-child-process--allow-fs-read--allow-fs-write--allow-wasi--allow-worker--build-snapshot--build-snapshot-config-C condition,--conditions=condition--cpu-prof--cpu-prof-dir--cpu-prof-interval--cpu-prof-name--disable-warning=code-or-type--expose-gc--env-file=config--experimental-default-type=type--experimental-detect-module--experimental-network-imports--experimental-permission--experimental-require-module--experimental-sea-config--experimental-shadow-realm--experimental-test-module-mocks--experimental-test-snapshots--frozen-intrinsics--heap-prof--heap-prof-dir--heap-prof-interval--heap-prof-name--heapsnapshot-near-heap-limit=max_count--import=module--jitless--no-experimental-global-navigator--run--snapshot-blob=path--test-update-snapshotsNODE_COMPILE_CACHE=dircrypto.hash(algorithm, data[, outputEncoding])socket[Symbol.asyncDispose]()diagnostics_channel.tracingChannel(nameOrChannels)channel.bindStore(store[, transform])channel.unbindStore(store)channel.runStores(context, fn[, thisArg[, ...args]])TracingChanneltracingChannel.subscribe(subscribers)tracingChannel.unsubscribe(subscribers)tracingChannel.traceSync(fn[, context[, thisArg[, ...args]]])tracingChannel.tracePromise(fn[, context[, thisArg[, ...args]]])tracingChannel.traceCallback(fn, position, context, thisArg, ...args)ERR_INPUT_TYPE_NOT_ALLOWEDERR_REQUIRE_CYCLE_MODULEERR_REQUIRE_ASYNC_MODULEERR_REQUIRE_ESMERR_UNKNOWN_FILE_EXTENSIONERR_UNKNOWN_MODULE_FORMATERR_USE_AFTER_CLOSEERR_NETWORK_IMPORT_BAD_RESPONSEERR_NETWORK_IMPORT_DISALLOWEDimport.meta.dirnameimport.meta.filenameimport.meta.resolve(specifier)events.addAbortListener(signal, listener)filehandle.readableWebStream([options])filehandle[Symbol.asyncDispose]()fsPromises.glob(pattern[, options])fs.glob(pattern[, options], callback)fs.openAsBlob(path[, options])fs.globSync(pattern[, options])dirent.parentPathByteLengthQueuingStrategyCompressionStreamCountQueuingStrategyCryptoCryptoKeyCustomEventDecompressionStreamNavigatorReadableByteStreamControllerReadableStreamReadableStreamBYOBReaderReadableStreamBYOBRequestReadableStreamDefaultControllerReadableStreamDefaultReaderSubtleCryptoTextDecoderStreamTextEncoderStream(Feel free to edit this table)