Just want to call out here, In .NET, we have an option to decide the behavior when filter can not be found: https://github.com/microsoft/FeatureManagement-Dotnet/blob/main/src/Microsoft.FeatureManagement/FeatureManagementOptions.cs The default behavior is throwing exception instead of slient error. And there was a discussion about this design: https://github.com/microsoft/FeatureManagement-Dotnet/issues/248 But it's not necessary to make JS FM lib completely same as .NET FM lib. Just put it here, for your reference. _Originally posted by @zhiyuanliang-ms in https://github.com/microsoft/FeatureManagement-JavaScript/pull/1#discussion_r1514055834_