Closed JayaKrishnaNamburu closed 10 months ago
Ah Good catch, tried it in my very old fork where the generator was like 1.0.2
:D and thought the same would have been now. Will change the import-map
too with the cli
. So, the generates maps from the deployed project can take advantage of it too 👍
If we upgrade this project to use the CLI that should fix the semantics here btw. Because the current chomp workflow doesn't behave the same as jspm install
I think, which should do a bump.
Yup, for now i am using cli
to manually bump the import-map
inside sandbox.html
file. Will create a separate issue to adopt the cli
for the project 👍. Waiting for the build to pass for the cdn
@JayaKrishnaNamburu is the CLI bumping the generator version or no? Did you try jspm update
?
There are few observations here
jspm update
seems to check for only imports
and not scopes
. And the repo is using @jspm/generator
under scopes. https://github.com/jspm/generator.jspm.io/blob/main/sandbox.html#L36@jspm/generator@1.1.10
seems to be stuck or failed or something. It is in the same status https://api.jspm.io/build/@jspm/generator@1.1.10@JayaKrishnaNamburu the build server is a little backlogged at the moment, hopefully our new server will be up in the next month to alleviate the load. I've triggered the build for the generator, it should be available now.
jspm update
checking only for imports seems correct to me. Perhaps we should reevaluate the import map here using the CLI so that it has the generator in imports?
jspm update checking only for imports seems correct to me. Perhaps we should reevaluate the import map here using the CLI so that it has the generator in imports?
Yup, exactly when the project is going to adopt the cli
by dropping the current way of import-maps generation using chomp
task. We should change the map a little 👍
Note that the generator version didn't actually bump here, because the import map is acting as a lock file.