Closed manuelroemer closed 11 months ago
Merging fix/cli-error-on-missing-dev-dependencies-on-win32 into develop impact files as follow:
Files | new size | |
---|---|---|
Unmodified (2) | 29.1 kB (0 B / +0%) | :ghost: |
Total (2) | 29.1 kB (0 B / +0%) | :ghost: |
Files | new size | |
---|---|---|
Unmodified (2) | 254 kB (0 B / +0%) | :ghost: |
Total (2) | 254 kB (0 B / +0%) | :ghost: |
Files | new size | |
---|---|---|
Unmodified (3) | 2.26 MB (0 B / +0%) | :ghost: |
Total (3) | 2.26 MB (0 B / +0%) | :ghost: |
Files | new size | |
---|---|---|
Unmodified (3) | 645 kB (0 B / +0%) | :ghost: |
Total (3) | 645 kB (0 B / +0%) | :ghost: |
Files | new size | |
---|---|---|
Unmodified (3) | 308 kB (0 B / +0%) | :ghost: |
Total (3) | 308 kB (0 B / +0%) | :ghost: |
Generated by @jsenv/file-size-impact during check-bundle-size#6656689626 on d7f2633
New Pull Request
For more information, see the
CONTRIBUTING
guide.Prerequisites
Please make sure you can check the following boxes:
Type(s) of Changes
Contribution Type
What types of changes does your code introduce? Put an
x
in all the boxes that apply:Description
We were running into an issue where the
pilet build ...
command failed building the pimon-portal sample project on the newest Piral version (1.3.2) on Windows. The output was simply:It seems that the error originated from the lack of a
devDependencies
section in the project's app shell package. Adding this section with an empty record{}
makes the build work again.I traced the error down by adding logs to the CLI's JS files and got this stack trace:
...which makes me think that adding the fallback in this PR could solve the issue. By using a
devDependencies
fallback of{}
,availableSpecs
is notundefined
and should then not cause the error inresolveImportmap > getDependencyDetails
.Remarks
None.