Open fsommar opened 2 years ago
/cc @mengqiy @yuwenma
This is part of efforts in https://github.com/GoogleContainerTools/kpt/issues/2874
This issue requires us to release npm modules for arm64 in the SDK repo. I will try to figure out how to fix it. @yuwenma Just FYI
I took a look at it. We need to restore something we removed in https://github.com/GoogleContainerTools/kpt-functions-sdk/pull/514. To be more concrete, we need to:
go/cmd/typegen
and go/pkg/swagger
. They should make typegen
have its own module.release-typegen.yaml
. Note that publish-bins.sh
has been moved to ts/scripts/publish-bins.sh
, so the last step needs to be updated.go/Makefile
and also add GOARCH=arm64
.
Hi 👋 I wasn't sure whether to mark this as a bug or a feature request, but given the increasing prevalence of M1 I opted for bug.
Expected behavior
The npm module
create-kpt-functions
should be usable on macOS arm64 architecture.Actual behavior
The npm module
create-kpt-functions
isn't usable on macOS arm64 architecture (M1) because the precompiledtypegen
binary is not available for darwin_arm64.Information
https://storage.googleapis.com/kpt-functions/v0.17.0/typegen_darwin_amd64.tar.gz
is available,https://storage.googleapis.com/kpt-functions/v0.17.0/typegen_darwin_arm64.tar.gz
is not. This leads to the following output when trying to runnpm install
in a project that has"create-kpt-functions": "^0.19.0"
as a dependency:Since we're only using it as a dev dependency I can at least run
npm install
after removing the dev dependency – but I'm still locked out of any workflows relying on the binary.Steps to reproduce the behavior
npm install
in a folder with thispackage.json
: