Adding NASM to buildcustomizations causes premake to depend on nasm and masm

[TracerDS]

I'm trying to generate VS2022 project with NASM integration.
In order to depend on nasm, I need the project to depend (via build customizations) on nasm.targets file.
However, here comes the problem:

When adding nasm entry to the buildcustomizations function, premake generates solution with dependency to both nasm AND masm. Thats not supposed to happen.

Premake5 version: 5.0.0-beta5

local projName = 'Test'

buildcustomizations { 'BuildCustomizations/nasm' }

workspace ( projName )
    configurations { 'Debug', 'Release' }
    platforms { 'x86', 'x64' }

    filter { "platforms:x86" }
        architecture "x86"

    filter { "platforms:x64" }
        architecture "x86_64"

    filter { 'configurations:Debug' }
        defines { 'DEBUG' }
        symbols 'On'

    filter { 'configurations:Release' }
        defines { 'NDEBUG' }
        optimize 'On'

    project ( projName )
        kind 'ConsoleApp'
        language 'C++'
        
        targetdir 'bin/%{cfg.buildcfg}'
        files { '*.asm' }