#1 Need to drop --bazel_patch_module_resolver 3 years ago

Comment by ~refi64 on ~refi64/web

Ryan Gonzalez referenced this ticket in commit 45ea98c.

REPORTED RESOLVED FIXED

#2 Migrating away from ts_library 3 years ago

Comment by ~refi64 on ~refi64/web

Ryan Gonzalez referenced this ticket in commit 5fb3418.

REPORTED RESOLVED FIXED

#2 Manually invoke PAM authentication 3 years ago

Ticket created by ~refi64 on ~refi64/nsbox

Using agetty here is a mess, it ends up printing some ugly login prompts to the journal every 30 seconds and relies on some serious hacks.

#1 Sort out unit testing 3 years ago

Ticket created by ~refi64 on ~refi64/nsbox

The current situation here is absolutely terrible, relying on very old Vagrant configs. Need to figure out the best way to handle this.

#3 Re-enable strict_visibility 3 years ago

Ticket created by ~refi64 on ~refi64/web

#2 Migrating away from ts_library 3 years ago

Ticket created by ~refi64 on ~refi64/web

It's not recommended by rules_nodejs anymore in favor of ts_project.

#1 Need to drop --bazel_patch_module_resolver 3 years ago

Ticket created by ~refi64 on ~refi64/web

Without it, module resolution breaks. Looks to be due to this issue which has some suggested fixes.