You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was going through the Hello World tutorial of the book, and ran into this error:
$ gren make src/Main.gren
Dependency problem!
-- PROBLEM BUILDING DEPENDENCIES (UNSIGNED KERNEL CODE) ------------------------
I ran into a compilation error when trying to build the following package:
gren-lang/url 2.0.0
This package contains kernel code which has not been signed by the lead
developer of Gren. Kernel code can violate all the guarantees that Gren provide,
and is therefore carefully managed.
Note: To help with the root problem, please report this to the package author.
The gren.json file that got generated by gren init:
Editing gren.json to bump the version of gren-lang/url to 2.0.1 fixed the error:
$ gren make src/Main.gren
Starting downloads...
● gren-lang/url 2.0.1
Dependencies ready!
Success! Compiled 1 module.
Main ───> index.html
The indirect dependency on gren-lang/url comes from gren-lang/browser. Maybe there should be a v2.0.1 release of gren-lang/browser with the minimum bound of the dependency constraint of gren-lang/url set to 2.0.1?
The text was updated successfully, but these errors were encountered:
ento
changed the title
Unsigned kernel code error when trying to compile a fresh project
Unsigned kernel code error when trying to compile a fresh browser project
Apr 8, 2023
I was going through the Hello World tutorial of the book, and ran into this error:
The
gren.json
file that got generated bygren init
:v2.0.1 of gren-lang/url appears to have a signature:
Editing
gren.json
to bump the version of gren-lang/url to 2.0.1 fixed the error:The indirect dependency on gren-lang/url comes from gren-lang/browser. Maybe there should be a v2.0.1 release of gren-lang/browser with the minimum bound of the dependency constraint of gren-lang/url set to 2.0.1?
The text was updated successfully, but these errors were encountered: