-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(vendor): support using an existing import map #14836
feat(vendor): support using an existing import map #14836
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested this in three repositories that use import maps, and it works correctly in all three. Very nice!
cli/tools/vendor/mod.rs
Outdated
"\nTo use vendored modules, specify the `--import-map {}` flag when ", | ||
r#"invoking deno subcommands or add an `"importMap": "<path_to_vendored_import_map>"` "#, | ||
"entry to your deno.json file.", | ||
), | ||
raw_output_dir.join("import_map.json").display(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is there an actual specifier for --import-map
, but not for <path_to_vendored_import_map>
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's more complicated and I didn't think it was worth it. It would require checking where the config is and then doing different logic for whether the config existed or didn't exist. Plus, now it auto updates the config file if it exists.
@dsherret any chance we can land that for v1.23? |
Take 2 (initial attempt was #14824).
./vendor
folder.Closes #13697