Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

feat: deno remove #24952

Merged
merged 10 commits into from
Aug 12, 2024
Merged

feat: deno remove #24952

merged 10 commits into from
Aug 12, 2024

Conversation

dsherret
Copy link
Member

@dsherret dsherret commented Aug 8, 2024

No description provided.

@satyarohith satyarohith added the ci-draft Run the CI on draft PRs. label Aug 9, 2024
@satyarohith satyarohith marked this pull request as ready for review August 9, 2024 08:19
@satyarohith satyarohith removed the ci-draft Run the CI on draft PRs. label Aug 9, 2024
@satyarohith satyarohith requested a review from bartlomieju August 9, 2024 09:31
Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just tried it. Works great with both deno.json and package.json.

One thing I noticed: if I add with deno add npm:chalk, I can't remove with deno rm npm:chalk; I have to use deno rm chalk. Not a big deal, but I think we could improve it further in the future.

LGTM!

Signed-off-by: Satya Rohith <me@satyarohith.com>
@satyarohith satyarohith enabled auto-merge (squash) August 10, 2024 18:53
@dsherret dsherret disabled auto-merge August 10, 2024 18:53
@dsherret
Copy link
Member Author

@satyarohith I want to take another look at this on Monday. I'll merge it then.

if cli_factory.cli_options()?.enable_future_features() {
crate::module_loader::load_top_level_deps(&cli_factory).await?;
}
crate::module_loader::load_top_level_deps(&cli_factory).await?;
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bartlomieju do you know why we feature gated this? I feel like we should be running this even without DENO_FUTURE?

@dsherret dsherret merged commit 085058c into denoland:main Aug 12, 2024
17 checks passed
@dsherret dsherret deleted the feat_deno_remove branch August 12, 2024 20:17
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants