Opened 7 years ago

Closed 7 years ago

#16294 closed defect (duplicate)

Allow composite package name (sub-packages)

Reported by: Philippe May Owned by:
Priority: undecided Milestone: tbd
Component: Loader Version: 1.8.1
Keywords: Cc:
Blocked By: Blocking:

Description

Nothing prevents from defining package names including a "/". However when doing so, the modules are not associated with their package in the build.

For a concrete example and use case: we want to have different packages developed by Alice and Bob, so we could have packages named "alice/pack1", "alice/pack2", "bob/pack1", with their resources "alice/pack1/package.json", "alice/pack1/main", etc.

Marking it as defect as i found no restriction in documentation, nor in the code, i assume it should be also considered as an enhancement as i can find many possibilities in allowing this construct, otherwise hard to achieve.

Attachments (1)

sub-packages-1-level.diff (696 bytes) - added by Philippe May 7 years ago.
Just a proof of concept: only one level, and matching should be other way (descendent, from most specific to most general)

Download all attachments as: .zip

Change History (2)

Changed 7 years ago by Philippe May

Attachment: sub-packages-1-level.diff added

Just a proof of concept: only one level, and matching should be other way (descendent, from most specific to most general)

comment:1 Changed 7 years ago by bill

Component: GeneralLoader
Resolution: duplicate
Status: newclosed

Duplicate of #15772.

Note: See TracTickets for help on using tickets.