refactor: Update the build workflow of the extensions using the inbuilt jspm build
command.
#19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue for the failing build is, because of a version bump that happened for
@babel/helper-module-transforms
package after the last release ofjspm-vscode
plugin which is0.2.1
8c4aa6d. All the maps i created started failing, so took thepacakge-lock.json
from the 0.2.1 version of the vs-code plugin and matched those versions to make things work and fix next.The build goes well when we are using
@babel/[email protected]
and failing when it uses the latest version of the package@babel/[email protected]
. I haven't looked deeply on what's changed between the two versions of this package.I created a new map using
it created a map using
@babel/[email protected]
which is expected as it falls into the@babel/core
range of the@jspm/generator
.Then i updated the map using to use
@babel/[email protected]
usingWhich gives us the current map in the PR
https://github.com/jspm/jspm-vscode/blob/c5136a0b87181fde37533149b6bbcc628def550a/importmap.json
Now i just used the build command to generate the build.
Which should work without any issues as we already stated the version to be
7.21.2
. But it fails again, turns outThe step where we load the
importmap
from the file into the generator and install it for the build to continue. Is updating everything againSee it here in the
jspm cli
https://github.com/jspm/jspm-cli/blob/main/src/build/rollup-importmap-plugin.ts#L18-L23
I am not sure if the
freeze
shouldn't even update theminor
andpatch
versions too. But, it's happening right now.So, i opened a new PR on the
cli
to make sure we pass resolutions and use them again at the step of installation.jspm/jspm-cli#2556
So, the new build command becomes
Which enforce the resolutions when using the existing map without updating the
minor
andpatch
for the package.Steps, we first need to release the cli and use it here and we are all good.
First implementation of the
jspm build
command in real time 😄fixes #17