Quick update: this new release candidate comes with extra breaking changes that can impact largely existing apps and the CLI build&deploy for SPAs. We will need more time to assess these and integrate this new Parcel release.
Meanwhile, the best workaround is still to create an app on the C drive.
davidbenge commentedAug 2, 2021
Describe the bug
With version 7.1.0 and 8.0.0 of CLI and app plugin if your project is in D: on windows 10 you will get this error when doing app run
error on run × Build failed.
@parcel/core: Unknown pipeline: ./C.
The fix is to move your project to C drive but that's not a good solution for our customers.
Thread on issue in slack
https://adobeio.slack.com/archives/CE7AW75QV/p1623719675113200
Thread with customer
https://experienceleaguecommunities.adobe.com/t5/project-firefly-questions/parcel-core/qaq-p/417895#M484
To Reproduce
Steps to reproduce the behavior:
@parcel/core: Unknown pipeline: ./C.
Expected behavior
aio app run should build and run the firefly application
Screenshots
See referenced threads above
Desktop (please complete the following information):
System:
OS: Windows 10 10.0.19042
CPU: (8) x64 Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Memory: 25.76 GB / 47.91 GB
Binaries:
Node: 14.17.0
Yarn: 1.22.5
npm: 6.14.13
Virtualization:
Docker: 20.10.6
npmGlobalPackages:
@adobe/aio-cli: Not Found
CLI plugins:
core:
@adobe/aio-cli 7.1.0
@adobe/aio-cli-plugin-app 7.0.2
@adobe/aio-cli-plugin-auth 2.4.1
@adobe/aio-cli-plugin-config 2.3.0
@adobe/aio-cli-plugin-console 3.3.0
@adobe/aio-cli-plugin-events 1.1.5
@adobe/aio-cli-plugin-info 2.0.0
@adobe/aio-cli-plugin-runtime 4.0.0
@oclif/plugin-autocomplete 0.3.0
@oclif/plugin-help 2.2.3
@oclif/plugin-not-found 1.2.4
@oclif/plugin-plugins 1.10.0
@oclif/plugin-warn-if-update-available 1.7.0
user:
@adobe/aio-cli-plugin-certificate 0.3.0 (*)
@adobe/aio-cli-plugin-doc 1.2.1
link:
Additional context
Add any other context about the problem here. There is another aio info in the experience league forum linked above.
The text was updated successfully, but these errors were encountered: