I've noticed deprecation warnings related to certain Babel plugins in my project's development environment. These warnings are indicating that the following Babel plugins have been deprecated due to their functionality being merged into the ECMAScript standard:
@babel/plugin-proposal-private-methods@babel/plugin-proposal-export-namespace-from@babel/plugin-proposal-unicode-property-regex@babel/plugin-proposal-optional-catch-binding@babel/plugin-proposal-nullish-coalescing-operator@babel/plugin-proposal-numeric-separator@babel/plugin-proposal-class-properties@babel/plugin-proposal-dynamic-import@babel/plugin-proposal-json-strings@babel/plugin-proposal-logical-assignment-operators@babel/plugin-proposal-class-static-block@babel/plugin-proposal-private-property-in-object@babel/plugin-proposal-optional-chaining@babel/plugin-proposal-object-rest-spread@babel/plugin-proposal-async-generator-functions
Issue Details:
These deprecation warnings are affecting the development process of my project, and I believe it's essential to keep the BeyondJS engine up to date with the latest JavaScript/ECMAScript standards and best practices.
I've noticed deprecation warnings related to certain Babel plugins in my project's development environment. These warnings are indicating that the following Babel plugins have been deprecated due to their functionality being merged into the ECMAScript standard:
@babel/plugin-proposal-private-methods@babel/plugin-proposal-export-namespace-from@babel/plugin-proposal-unicode-property-regex@babel/plugin-proposal-optional-catch-binding@babel/plugin-proposal-nullish-coalescing-operator@babel/plugin-proposal-numeric-separator@babel/plugin-proposal-class-properties@babel/plugin-proposal-dynamic-import@babel/plugin-proposal-json-strings@babel/plugin-proposal-logical-assignment-operators@babel/plugin-proposal-class-static-block@babel/plugin-proposal-private-property-in-object@babel/plugin-proposal-optional-chaining@babel/plugin-proposal-object-rest-spread@babel/plugin-proposal-async-generator-functionsIssue Details:
These deprecation warnings are affecting the development process of my project, and I believe it's essential to keep the BeyondJS engine up to date with the latest JavaScript/ECMAScript standards and best practices.