[NPMBUILD-3] magnolia-build copy module into resources folder including package.json Created: 25/Jan/16  Updated: 16/Mar/17

Status: Accepted
Project: Magnolia light-module build tools
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Tomáš Gregovský Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: to-specify
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

magnolia-build copy module into resources folder including package.json that one is then visible in magnolia resources app... and simply shouldn't be copied. I guess similar for some kind on readme files, etc... maybe just folders should be? or something like ignore list in magnolia-build package.json?



 Comments   
Comment by Espen Jervidalo [ 27/Jan/16 ]

This is debatable. But worth a discussion. It's also something we can decide later on. The files do no harm and the package.json also provides useful information, at least as long as there's no other way to see dependencies or version, etc..

Comment by Michael Mühlebach [ 16/Mar/17 ]

As there is no clear agreement on this ticket I removed it from the backlog. If it is still required please discuss this in architecture + pm so we can fill in the missing details and answer the open questions before we add it back to the backlog.

Generated at Mon Feb 12 06:00:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.