Project build error on current node/go version
See original GitHub issueHello, I’m trying to build the project, by following the procedure in README.md, but faced on error.
Steps to Reproduce
lerna ERR! yarn run build stdout:
$ tsc
$ node ./lib/__tests__/edge-provider-schema/cli.js ./edge-provider-bindings
The attribute isn't implemented yet: {"storageName":"_boolList","_name":"boolList","type":{"_type":"boolean","typeName":"boolean","isList":true,"isSet":false,"isMap":false,"isComputed":false,"isOptional":false,"isRequired":true,"isSingleItem":false,"level":2,"isNested":false},"optional":false,"computed":false,"terraformName":"boolList","terraformFullName":"edge.required_attribute_resource.boolList","provider":false,"required":true}
The attribute isn't implemented yet: {"storageName":"_boolList","_name":"boolList","type":{"_type":"boolean","typeName":"boolean","isList":true,"isSet":false,"isMap":false,"isComputed":false,"isOptional":true,"isRequired":false,"isSingleItem":false,"level":2,"isNested":false},"optional":true,"computed":false,"terraformName":"boolList","terraformFullName":"edge.optional_attribute_resource.boolList","provider":false,"required":false}
The attribute isn't implemented yet: {"storageName":"_boolList","_name":"boolList","type":{"_type":"boolean","typeName":"boolean","isList":true,"isSet":false,"isMap":false,"isComputed":true,"isOptional":true,"isRequired":false,"isSingleItem":false,"level":2,"isNested":false},"optional":true,"computed":true,"terraformName":"boolList","terraformFullName":"edge.optional_computed_attribute_resource.boolList","provider":false,"required":false}
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
lerna ERR! yarn run build stderr:
node:internal/process/promises:279
triggerUncaughtException(err, true /* fromPromise */);
^
[LinkError: WebAssembly.instantiate(): Import #5 module="go" function="runtime.walltime" error: function import requires a callable]
error Command failed with exit code 1.
lerna ERR! yarn run build exited 1 in '@cdktf/provider-generator'
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Environment
- OS: MacOS (M1)
- Node: 16.15.1
- Golang: 1.18
Issue Analytics
- State:
- Created a year ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Upgrading node version throws node-sass error when trying ...
I am currently running a Node v10.19.0 / Nextjs8 project locally. I want to further upgrade the Next version to 11. I start...
Read more >node-pre-gyp build fail error while installing with npm ... - GitHub
Any current version of Node.js 14, 12 or 10 should contain a version of npm that includes a version of node-gyp with Python...
Read more >Set up Node.js on WSL 2 - Windows - Microsoft Learn
A guide to help you get your Node.js development environment set up on Windows Subsystem for Linux (WSL).
Read more >Error: Module build failed: Error: Node Sass does not yet ...
This error happened with me after upgrade of node.js. Cause: Node Sass version is not compatible with Node.js version. Solution: you should check...
Read more >check-node-version - npm
Check installed versions of node and npm. Latest version: 4.2.1, last published: a year ago. Start using check-node-version in your project ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@kination at this time only go version 1.16 is supported. Take a look here for more info. (Please keep this issue open though)
I’m going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you’ve found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.