Closed Pangoraw closed 3 years ago
You closed this but we should rename it to DenoJS.jl right? Or we get permission to skip the rule, like JSON.jl.
Though, unline node, deno is never called "deno js", and it also a TS runtime..... hmm
I was advised to release it as a _jll package since NodeJS.jl is moving to a _jll as well :smiley: . See Deno_jll.jl, the source for generating the package are located in Yggdrasil I don't think there is much value in keeping a thin wrapper around the jll package, what do you think?
(@v1.6) pkg> activate --temp
Activating new environment at `/tmp/jl_tKnHUh/Project.toml`
(jl_tKnHUh) pkg> add Deno_jll@1.10.1
Updating registry at `~/.julia/registries/General`
Updating git-repo `https://github.com/JuliaRegistries/General.git`
Resolving package versions...
Updating `/tmp/jl_tKnHUh/Project.toml`
[04572ae6] + Deno_jll v1.10.1+0
Updating `/tmp/jl_tKnHUh/Manifest.toml`
[692b3bcd] + JLLWrappers v1.3.0
...
[3f19e933] + p7zip_jll
julia> using Deno_jll
julia> deno() do exe
run(`$exe`)
end
Deno 1.10.1
exit using ctrl+d or close()
>
As per the registry guidelines, the package name must be at least 5 characters long:
Should we rename the package to something like
DenoJS.jl
?