how to avoid deprecation warnings in compiled binaries
What I don’t get is that when I compile it locally I don’t get these warnings. Only in the CI/CD produced binaries.
Which means I didn’t see this, but all my users did.
MNote, that I have fixed the deprecation warnings and intend to release a point release. I am just trying to ensure that in the future I don’t deliver my users a bunch of warnings they don't care about
DTo avoid deprecation warnings in compiled binaries, you should ensure that your code does not use any deprecated APIs. The warnings you're seeing (, , and ) indicate that these APIs are deprecated and will be removed in Deno 2.
Here are some steps you can take to address the deprecation warnings:
Here are some steps you can take to address the deprecation warnings:
- Update Your Code: Replace the deprecated APIs with their recommended alternatives. For example, instead of using , you can use the new as a . Similarly, replace with the new API if available.
- Ensure Consistent Deno Versions: Make sure that the Deno version used in your local development environment is the same as the one used in your CI/CD pipeline. This will help you catch deprecation warnings early.
- Run with Verbose Warnings: To get more details about the deprecation warnings, you can run your code with the environment variable set. This might provide additional information on what needs to be changed.
- Check Release Notes: Refer to the Deno release notes for the version you are using to see if there are any breaking changes or deprecations that affect your code. The documentation mentions that has been renamed to in Deno 1.19, for example, so you should check for similar notes regarding the APIs you are using.
- Compile with the Latest Deno Version: Before compiling your code, make sure you are using the latest stable version of Deno. This ensures that you have all the latest features and deprecation notices.
- Test Binaries Before Release: Test the compiled binaries in an environment similar to your users' to catch any warnings or issues that might not appear in your
Ddevelopment environment.
If you've updated your code and are still seeing these warnings in the CI/CD pipeline but not locally, it's possible that the Deno version in the CI/CD environment is different from your local version, or there might be some environment-specific differences causing these warnings to show up. Ensure that the Deno version is consistent across environments and that you're testing the binaries in a clean environment that mimics your users' setups as closely as possible.
Remember, it's important to address these warnings before Deno 2 is released, as the deprecated APIs will be removed, potentially breaking your application if it still relies on them.
If you've updated your code and are still seeing these warnings in the CI/CD pipeline but not locally, it's possible that the Deno version in the CI/CD environment is different from your local version, or there might be some environment-specific differences causing these warnings to show up. Ensure that the Deno version is consistent across environments and that you're testing the binaries in a clean environment that mimics your users' setups as closely as possible.
Remember, it's important to address these warnings before Deno 2 is released, as the deprecated APIs will be removed, potentially breaking your application if it still relies on them.
MI cannot remove all the deprecated API usages. I need to use the dnt tool to publish to npm which does not yet support all the deprecated APIs
Mbasically you are saying using deno means we cannot avoid announcing to the user about deprecated APIs in a compiled binary
MAdditionally we absolutely there is no way we can see to not use some of the deprecated APIs, eg. the unstable API for flock which we use has not been updated, it still requires a
Mfor now we will pin to 1.39
AI think there is something like --quiet, not sure, check the docs.
L