Skip to content

[FEATURE] Ability to specify composer packages manually - #26

Draft
s2b wants to merge 1 commit into
mainfrom
feature/manualComposer
Draft

[FEATURE] Ability to specify composer packages manually#26
s2b wants to merge 1 commit into
mainfrom
feature/manualComposer

Conversation

@s2b

@s2b s2b commented Sep 10, 2025

Copy link
Copy Markdown
Owner

A new config option is introduced, which allows to bypass the automatic
package discovery and to supply the package paths manually.

Resolves: #21

@s2b
s2b force-pushed the feature/manualComposer branch 2 times, most recently from bbe9cc8 to 3323ea5 Compare September 13, 2025 10:40
@s2b s2b changed the title WIP: [FEATURE] Ability to specify composer packages manually [FEATURE] Ability to specify composer packages manually Sep 13, 2025
@s2b
s2b marked this pull request as ready for review September 13, 2025 10:41
@s2b
s2b force-pushed the feature/manualComposer branch 2 times, most recently from 87947f7 to f3f7cbf Compare September 13, 2025 10:49
@s2b
s2b force-pushed the feature/manualComposer branch 2 times, most recently from 44567bc to eaa093e Compare March 22, 2026 11:20
A new config option is introduced, which allows to bypass the automatic
package discovery and to supply the package paths manually.

Resolves: #21
@s2b
s2b force-pushed the feature/manualComposer branch from eaa093e to 7a83832 Compare March 22, 2026 12:05
@s2b
s2b marked this pull request as draft March 22, 2026 12:06
@s2b

s2b commented Mar 22, 2026

Copy link
Copy Markdown
Owner Author

This approach currently doesn't work because it creates unsuitable asset identifiers in the manifest.json with resolve.preserveSymlinks = true (see #28)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Discussion: Composer requirement

1 participant