<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:15:19 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-1707] platform-complete webpack build is broken</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-1707</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;Currently, a build of platform-complete results in most (all?) apps displaying an error page:&lt;br/&gt;
 &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;64122_thumb&quot; href=&quot;/rest/api/3/attachment/content/64122&quot; title=&quot;Screen Shot 2019-01-16 at 1.12.38 PM.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;64122&quot; file-preview-title=&quot;Screen Shot 2019-01-16 at 1.12.38 PM.png&quot;&gt;&lt;jira-attachment-thumbnail url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/64122?default=false&quot; jira-url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/64122&quot; filename=&quot;Screen Shot 2019-01-16 at 1.12.38 PM.png&quot;&gt;&lt;img src=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/64122&quot; data-attachment-name=&quot;Screen Shot 2019-01-16 at 1.12.38 PM.png&quot; data-attachment-type=&quot;thumbnail&quot; data-media-services-id=&quot;aa213b32-267e-42fb-898a-e54c86086e00&quot; data-media-services-type=&quot;file&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/jira-attachment-thumbnail&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A3d5df1a2-9ff6-4d03-b1b0-7d6b01378729&quot; class=&quot;user-hover&quot; rel=&quot;712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729&quot; data-account-id=&quot;712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729&quot; accountid=&quot;712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729&quot; rel=&quot;noreferrer&quot;&gt;Jeffrey Cherewaty&lt;/a&gt; points out that the dependency on platform-core expressed in the platform-complete &lt;tt&gt;package.json&lt;/tt&gt; file resolves to an old npm package of platform core (v1.1.1) when using the npm-folioci repo (see 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1706&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1706&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;platform-complete build from npm-folioci pulls in ancient platform-core package&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-1706
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
). This may or may not be the root of the issue. &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt; experienced the same issue building platform-core directly from a git checkout.&lt;/p&gt;</description>
                <environment></environment>
        <key id="80905">FOLIO-1707</key>
            <summary>platform-complete webpack build is broken</summary>
                <type id="10001" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium">Bug</type>
                                            <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="557058:624212b9-5938-4e3b-84c6-8c8a8db84996">Matthew Jones</assignee>
                                                                <reporter accountid="5c706fbb47a54a6728e59df2">Wayne Schneider</reporter>
                                    <labels>
                    </labels>
                <created>Wed, 16 Jan 2019 19:20:28 +0000</created>
                <updated>Wed, 3 Jun 2020 16:39:23 +0000</updated>
                            <resolved>Wed, 16 Jan 2019 22:57:20 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                <comments>
                                                            <comment id="194340" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Wed, 16 Jan 2019 19:55:41 +0000"  >&lt;p&gt;The old platform-core may be causing grief for platform-complete, but we still have build issues with platform-core#snapshot in isolation.  This appears to be due to multiple versions of stripes&amp;#45;&amp;#42; modules unexpectedly leaking into the build.  The build provides warnings for this, but they should be errors.  Errors would have failed the build catching this slightly sooner.  Its a simple configuration change to switch that, but either way we still have the issue.&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;WARNING in @folio/stripes-components
  Multiple versions of @folio/stripes-components found:
    4.5.1000698 ./~/@folio/stripes-components
    5.0.1000700 ./~/@folio/stripes/~/@folio/stripes-smart-components/~/@folio/stripes-form/~/@folio/stripes-components


WARNING in @folio/stripes-core
  Multiple versions of @folio/stripes-core found:
    2.17.1000488 ./~/@folio/stripes-core
    3.0.1000489 ./~/@folio/stripes-connect/~/@folio/stripes-core


WARNING in @folio/stripes-form
  Multiple versions of @folio/stripes-form found:
    1.2.100039 ./~/@folio/stripes/~/@folio/stripes-form
    1.3.100040 ./~/@folio/stripes/~/@folio/stripes-smart-components/~/@folio/stripes-form
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="194342" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Wed, 16 Jan 2019 20:03:34 +0000"  >&lt;p&gt;Looking into the &lt;b&gt;yarn why&lt;/b&gt; output for stripes-components:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;$ yarn why @folio/stripes-components
yarn why v1.12.3
warning package.json: &quot;dependencies&quot; has dependency &quot;react&quot; with range &quot;^16.6.3&quot; that collides with a dependency in &quot;devDependencies&quot; of the same name with version &quot;~16.6.0&quot;
warning package.json: &quot;dependencies&quot; has dependency &quot;react-dom&quot; with range &quot;^16.6.3&quot; that collides with a dependency in &quot;devDependencies&quot; of the same name with version &quot;~16.6.0&quot;
warning package.json: &quot;dependencies&quot; has dependency &quot;react-redux&quot; with range &quot;^5.1.1&quot; that collides with a dependency in &quot;devDependencies&quot; of the same name with version &quot;~5.1.1&quot;
warning package.json: &quot;dependencies&quot; has dependency &quot;redux&quot; with range &quot;^3.7.2&quot; that collides with a dependency in &quot;devDependencies&quot; of the same name with version &quot;~3.7.2&quot;
[1/4]   Why do we have the module &quot;@folio/stripes-components&quot;...?
[2/4]   Initialising dependency graph...
warning @folio/platform-core@1.1.2-SNAPSHOT: &quot;dependencies&quot; has dependency &quot;react&quot; with range &quot;^16.6.3&quot; that collides with a dependency in &quot;devDependencies&quot; of the same name with version &quot;~16.6.0&quot;
warning @folio/platform-core@1.1.2-SNAPSHOT: &quot;dependencies&quot; has dependency &quot;react-dom&quot; with range &quot;^16.6.3&quot; that collides with a dependency in &quot;devDependencies&quot; of the same name with version &quot;~16.6.0&quot;
warning @folio/platform-core@1.1.2-SNAPSHOT: &quot;dependencies&quot; has dependency &quot;react-redux&quot; with range &quot;^5.1.1&quot; that collides with a dependency in &quot;devDependencies&quot; of the same name with version &quot;~5.1.1&quot;
warning @folio/platform-core@1.1.2-SNAPSHOT: &quot;dependencies&quot; has dependency &quot;redux&quot; with range &quot;^3.7.2&quot; that collides with a dependency in &quot;devDependencies&quot; of the same name with version &quot;~3.7.2&quot;
[3/4]   Finding dependency...
[4/4]   Calculating file sizes...
=&amp;gt; Found &quot;@folio/stripes-components@4.5.1000698&quot;
info Has been hoisted to &quot;@folio/stripes-components&quot;
info Reasons this module exists
   - Hoisted from &quot;@folio#stripes-core#@folio#stripes-components&quot;
   - Hoisted from &quot;@folio#stripes#@folio#stripes-components&quot;
   - Hoisted from &quot;@folio#stripes#@folio#stripes-form#@folio#stripes-components&quot;
   - Hoisted from &quot;@folio#stripes#@folio#stripes-smart-components#@folio#stripes-components&quot;
info Disk size without dependencies: &quot;8.05MB&quot;
info Disk size with unique dependencies: &quot;39.22MB&quot;
info Disk size with transitive dependencies: &quot;75.79MB&quot;
info Number of shared dependencies: 51
=&amp;gt; Found &quot;@folio/stripes-cli#@folio/stripes-components@5.0.1000700&quot;
info Reasons this module exists
   - &quot;@folio#stripes-cli#@folio#stripes-core&quot; depends on it
   - Hoisted from &quot;@folio#stripes-cli#@folio#stripes-core#@folio#stripes-components&quot;
info Disk size without dependencies: &quot;7.79MB&quot;
info Disk size with unique dependencies: &quot;38.96MB&quot;
info Disk size with transitive dependencies: &quot;75.53MB&quot;
info Number of shared dependencies: 51
=&amp;gt; Found &quot;@folio/stripes-connect#@folio/stripes-components@5.0.1000700&quot;
info Reasons this module exists
   - &quot;@folio#stripes-connect#@folio#stripes-core&quot; depends on it
   - Hoisted from &quot;@folio#stripes-connect#@folio#stripes-core#@folio#stripes-components&quot;
info Disk size without dependencies: &quot;7.79MB&quot;
info Disk size with unique dependencies: &quot;38.96MB&quot;
info Disk size with transitive dependencies: &quot;75.53MB&quot;
info Number of shared dependencies: 51
=&amp;gt; Found &quot;@folio/stripes-smart-components#@folio/stripes-form#@folio/stripes-components@5.0.1000700&quot;
info Reasons this module exists
   - &quot;@folio#stripes#@folio#stripes-smart-components#@folio#stripes-form&quot; depends on it
   - Hoisted from &quot;@folio#stripes#@folio#stripes-smart-components#@folio#stripes-form#@folio#stripes-core#@folio#stripes-components&quot;
Done in 2.38s.
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="194348" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Wed, 16 Jan 2019 20:11:09 +0000"  >&lt;p&gt;Given this snippet from the why output:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;=&amp;gt; Found &quot;@folio/stripes-connect#@folio/stripes-components@5.0.1000700&quot;
info Reasons this module exists
   - &quot;@folio#stripes-connect#@folio#stripes-core&quot; depends on it
   - Hoisted from &quot;@folio#stripes-connect#@folio#stripes-core#@folio#stripes-components&quot;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I wonder if the relaxed version range within stripes-connect has something to do with it.&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
  &lt;span class=&quot;code-quote&quot;&gt;&quot;@folio/stripes-core&quot;&lt;/span&gt;: &lt;span class=&quot;code-quote&quot;&gt;&quot;^2.15.0 || ^3.0.0&quot;&lt;/span&gt;,
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;This was chosen in part to help facilitate the transition and deal with a circular dependency that exists within the &lt;tt&gt;stripes-*&lt;/tt&gt; modules.  However, it would seem that the version range is acting greedy, pulling in 3.x of core and in turn, 5.x of components, when not necessary. &lt;/p&gt;</comment>
                                                            <comment id="194351" author="712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729" created="Wed, 16 Jan 2019 20:13:37 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A624212b9-5938-4e3b-84c6-8c8a8db84996&quot; class=&quot;user-hover&quot; rel=&quot;557058:624212b9-5938-4e3b-84c6-8c8a8db84996&quot; data-account-id=&quot;557058:624212b9-5938-4e3b-84c6-8c8a8db84996&quot; accountid=&quot;557058:624212b9-5938-4e3b-84c6-8c8a8db84996&quot; rel=&quot;noreferrer&quot;&gt;Matthew Jones&lt;/a&gt; I can tag a new &lt;tt&gt;stripes-connect&lt;/tt&gt; to resolve that.&lt;/p&gt;

&lt;p&gt;Should we lock in &lt;tt&gt;platform-core&lt;/tt&gt;&apos;s &lt;tt&gt;stripes-cli&lt;/tt&gt; with a &lt;tt&gt;~&lt;/tt&gt; instead of &lt;tt&gt;&amp;gt;=&lt;/tt&gt; too?&lt;/p&gt;</comment>
                                                            <comment id="194353" author="712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729" created="Wed, 16 Jan 2019 20:16:57 +0000"  >&lt;p&gt;Wait but why was that newer &lt;tt&gt;stripes-connect&lt;/tt&gt; in there &lt;img class=&quot;emoticon&quot; src=&quot;/images/icons/emoticons/sad.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                                                            <comment id="194356" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Wed, 16 Jan 2019 20:22:32 +0000"  >&lt;p&gt;Good question...&lt;/p&gt;

&lt;p&gt;We did expect some issues in snapshot to surface during the rollout (in terms of ui-* module peerDependency warnings), but not this mixing of multiple stripes modules.  Come to think of it, should our &lt;tt&gt;stripes&amp;#45;&amp;#42;&lt;/tt&gt; depend on each other as peerDependencies?  This may be the fundamental issue.&lt;/p&gt;

&lt;p&gt;For instance, ui-users will pull in whatever stripes framework it was given because of the peerDependency is fulfilled by the platform. Further, any import for stripes-* by ui-modules must go through the framework ensuring all apps use the same version.  Stripes modules however, have direct dependencies on each other and it seems that those links may be where the multiple versions are sneaking in.&lt;/p&gt;

&lt;p&gt;Here is the yarn why for connect:&lt;/p&gt;


&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;=&amp;gt; Found &quot;@folio/stripes-connect@3.4.100059&quot;
info Has been hoisted to &quot;@folio/stripes-connect&quot;
info Reasons this module exists
   - Hoisted from &quot;@folio#stripes-core#@folio#stripes-connect&quot;
   - Hoisted from &quot;@folio#stripes#@folio#stripes-smart-components#@folio#stripes-connect&quot;
   - Hoisted from &quot;@folio#stripes-cli#@folio#stripes-core#@folio#stripes-connect&quot;
   - Hoisted from &quot;@folio#stripes-connect#@folio#stripes-core#@folio#stripes-connect&quot;
   - Hoisted from &quot;@folio#stripes#@folio#stripes-smart-components#@folio#stripes-form#@folio#stripes-core#@folio#stripes-connect&quot;
info Disk size without dependencies: &quot;10.64MB&quot;
info Disk size with unique dependencies: &quot;19.08MB&quot;
info Disk size with transitive dependencies: &quot;327.66MB&quot;
info Number of shared dependencies: 332
=&amp;gt; Found &quot;@folio/stripes#@folio/stripes-connect@3.3.100058&quot;
info This module exists because &quot;@folio#stripes&quot; depends on it.
info Disk size without dependencies: &quot;212KB&quot;
info Disk size with unique dependencies: &quot;8.64MB&quot;
info Disk size with transitive dependencies: &quot;317.22MB&quot;
info Number of shared dependencies: 332
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The framework has the correct version, but the other stripes-* modules do not.&lt;/p&gt;</comment>
                                                            <comment id="194361" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Wed, 16 Jan 2019 20:27:22 +0000"  >&lt;p&gt;But still, those stripes-* modules should be originating from within stripes framework and therefore we should have all the versions locked down accordingly.&lt;/p&gt;</comment>
                                                            <comment id="194364" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Wed, 16 Jan 2019 20:30:28 +0000"  >&lt;p&gt;Oh but wait, stripes-connect 3.4, not being a major version change, can be fulfilled by any carat &lt;tt&gt;^&lt;/tt&gt; version ranges requested of it by other stripes-* modules.  &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A3d5df1a2-9ff6-4d03-b1b0-7d6b01378729&quot; class=&quot;user-hover&quot; rel=&quot;712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729&quot; data-account-id=&quot;712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729&quot; accountid=&quot;712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729&quot; rel=&quot;noreferrer&quot;&gt;Jeffrey Cherewaty&lt;/a&gt; that must be it.&lt;/p&gt;</comment>
                                                            <comment id="194366" author="712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729" created="Wed, 16 Jan 2019 20:40:06 +0000"  >&lt;p&gt;What if we did this with `stripes-cli`?&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Release &lt;tt&gt;v1.8.1&lt;/tt&gt; that reverts &lt;a href=&quot;https://github.com/folio-org/stripes-cli/pull/158&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/stripes-cli/pull/158&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;Release &lt;tt&gt;v2.0.0&lt;/tt&gt; that requires &lt;tt&gt;stripes-core&lt;/tt&gt; &lt;tt&gt;3.x&lt;/tt&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;I think that might stop the newer &lt;tt&gt;stripes-core&lt;/tt&gt; and its resulting cascade from coming in.&lt;/p&gt;</comment>
                                                            <comment id="194368" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Wed, 16 Jan 2019 20:43:16 +0000"  >&lt;p&gt;I don&apos;t think that will be the culprit.  The CLI has logic to detect and use the ui-module or platform&apos;s version of stripes-core rather than its own, for performing builds.  Effectively, the CLI will only use its own copy of stripes-core, when no other stripes-core is present (for example, building a brand new app with a global install of the CLI)&lt;/p&gt;</comment>
                                                            <comment id="194373" author="712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729" created="Wed, 16 Jan 2019 20:43:28 +0000"  >&lt;p&gt;&lt;del&gt;Unfortunately I think we&apos;ll have to bump major versions of &lt;tt&gt;stripes-cli&lt;/tt&gt; with &lt;tt&gt;stripes&lt;/tt&gt;.&lt;/del&gt; Marked out so future readers of this know this is wrong. &lt;img class=&quot;emoticon&quot; src=&quot;/images/icons/emoticons/biggrin.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                                                            <comment id="194376" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Wed, 16 Jan 2019 20:45:16 +0000"  >&lt;p&gt;I&apos;m doing some more tests, but it looks like stripes-form1.3, not being a major version bump, could equally suffer from the same carat ^ version range issue when requested by other stripes-* modules, allowing its dependency of stripes-components 5.0 to leak.&lt;/p&gt;
</comment>
                                                            <comment id="194379" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Wed, 16 Jan 2019 21:05:00 +0000"  >&lt;p&gt;Okay, if I lock stripes-connect and stripes-form to their previously published minor versions, my local platform-core builds without any duplicate stripes warnings and appears to render the application without trouble.  I did this by adding the following yarn resolutions to platform-core&apos;s package.json to simulate rolling back:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
&lt;span class=&quot;code-quote&quot;&gt;&quot;resolutions&quot;&lt;/span&gt;: {
    &lt;span class=&quot;code-quote&quot;&gt;&quot;@folio/stripes-connect&quot;&lt;/span&gt;: &lt;span class=&quot;code-quote&quot;&gt;&quot;~3.3.1&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;@folio/stripes-form&quot;&lt;/span&gt;: &lt;span class=&quot;code-quote&quot;&gt;&quot;~1.2.0&quot;&lt;/span&gt;
  }
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Yarn why still reports duplicates on disk due to stripes-cli allowing for stripes-core 3.x.  However, I&apos;m confident the CLI is not pulling in its own copy stripes-core for generating bundles.  Long before stripes framework came about, the possible discrepancy of stripes-core version between the CLI and ui-module/platform being built had surfaced.  This was address by 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;STCLI-27&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/STCLI-27&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Support local stripes-core at build-time&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            STCLI-27
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 and released in v1.1.0.&lt;/p&gt;</comment>
                                                            <comment id="194383" author="712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729" created="Wed, 16 Jan 2019 21:06:09 +0000"  >&lt;p&gt;Cool, I&apos;m going to make these PRs/tags:&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;stripes-connect&lt;/tt&gt; &lt;tt&gt;3.4.1&lt;/tt&gt; (reversion) and &lt;tt&gt;4.0.0&lt;/tt&gt;&lt;br/&gt;
&lt;tt&gt;stripes-form&lt;/tt&gt; &lt;tt&gt;1.3.1&lt;/tt&gt; (reversion) and &lt;tt&gt;2.0.0&lt;/tt&gt;&lt;/p&gt;</comment>
                                                            <comment id="194385" author="712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729" created="Wed, 16 Jan 2019 21:16:05 +0000"  >&lt;p&gt;&lt;a href=&quot;https://github.com/folio-org/stripes-connect/pull/70&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/stripes-connect/pull/70&lt;/a&gt; and &lt;a href=&quot;https://github.com/folio-org/stripes-form/pull/44&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/stripes-form/pull/44&lt;/a&gt; should resolve this when tagged and published.&lt;/p&gt;

&lt;p&gt;Then I&apos;ll make the new major version bumps when confirmed.&lt;/p&gt;</comment>
                                                            <comment id="194389" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Wed, 16 Jan 2019 21:34:24 +0000"  >&lt;p&gt;Awesome. &lt;/p&gt;

&lt;p&gt;FYI, in npm-folioci-speak, the affected artifact versions are:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;stripes-connect 3.4.100059
stripes-form 1.3.100040
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The corrected versions are:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;stripes-connect 3.4.100060
stripes-form 1.3.100041
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I&apos;m running a build with them now.&lt;/p&gt;</comment>
                                                            <comment id="194392" author="712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729" created="Wed, 16 Jan 2019 21:44:12 +0000"  >&lt;p&gt;Still getting:&lt;br/&gt;
&lt;tt&gt;=&amp;gt; Found &quot;@folio/stripes-cli#@folio/stripes-core@3.0.1000489&quot;&lt;/tt&gt;&lt;br/&gt;
&lt;tt&gt;info This module exists because &quot;@folio#stripes-cli&quot; depends on it.&lt;/tt&gt;&lt;/p&gt;</comment>
                                                            <comment id="194395" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Wed, 16 Jan 2019 21:49:33 +0000"  >&lt;p&gt;Yes, that&apos;s expected because yarn why is only looking at what is available on disk.  The duplicate checker plugin will confirm whether or not a duplicate module was pulled into the bundle.  In this case, stripes-core is not duplicated.  There is, however, one duplicate stripes-form warning upon build:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;WARNING in @folio/stripes-form
  Multiple versions of @folio/stripes-form found:
    1.2.100039 ./~/@folio/stripes/~/@folio/stripes-form
    1.3.100041 ./~/@folio/stripes/~/@folio/stripes-smart-components/~/@folio/stripes-form
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;This can be attributed to the stripes framework locking down stripes-form at 1.2.x and smart-components accepting minor version changes.&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;=&amp;gt; Found &quot;@folio/stripes-form@1.2.100039&quot;
info Reasons this module exists
   - &quot;@folio#stripes&quot; depends on it
   - Hoisted from &quot;@folio#stripes#@folio#stripes-form&quot;
=&amp;gt; Found &quot;@folio/stripes-smart-components#@folio/stripes-form@1.3.100041&quot;
info This module exists because &quot;@folio#stripes#@folio#stripes-smart-components&quot; depends on it.
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The good news is that those two versions, 1.2.100039 and 1.3.100041, should be equivalent with the latter reflecting the rollback.&lt;/p&gt;

&lt;p&gt;I&apos;ve installed the latest updates with platform core and aside from that warning everything appears to run fine.&lt;/p&gt;</comment>
                                                            <comment id="194400" author="712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729" created="Wed, 16 Jan 2019 22:02:57 +0000"  >&lt;p&gt;Makes sense, yeah, it&apos;s fine that those are just on the disk.&lt;/p&gt;

&lt;p&gt;Major version PRs open for &lt;tt&gt;stripes-form&lt;/tt&gt; &lt;a href=&quot;https://github.com/folio-org/stripes-form/pull/45&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/stripes-form/pull/45&lt;/a&gt; and &lt;tt&gt;stripes-connect&lt;/tt&gt; &lt;a href=&quot;https://github.com/folio-org/stripes-connect/pull/71&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/stripes-connect/pull/71&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="194402" author="5c706fbb47a54a6728e59df2" created="Wed, 16 Jan 2019 22:57:12 +0000"  >&lt;p&gt;Latest CI build is now working...thanks, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A3d5df1a2-9ff6-4d03-b1b0-7d6b01378729&quot; class=&quot;user-hover&quot; rel=&quot;712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729&quot; data-account-id=&quot;712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729&quot; accountid=&quot;712020:3d5df1a2-9ff6-4d03-b1b0-7d6b01378729&quot; rel=&quot;noreferrer&quot;&gt;Jeffrey Cherewaty&lt;/a&gt; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A624212b9-5938-4e3b-84c6-8c8a8db84996&quot; class=&quot;user-hover&quot; rel=&quot;557058:624212b9-5938-4e3b-84c6-8c8a8db84996&quot; data-account-id=&quot;557058:624212b9-5938-4e3b-84c6-8c8a8db84996&quot; accountid=&quot;557058:624212b9-5938-4e3b-84c6-8c8a8db84996&quot; rel=&quot;noreferrer&quot;&gt;Matthew Jones&lt;/a&gt;!&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="80904">FOLIO-1706</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="61377">STRIPES-588</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="64122" name="Screen Shot 2019-01-16 at 1.12.38 PM.png" size="199330" author="5c706fbb47a54a6728e59df2" created="Wed, 16 Jan 2019 19:13:03 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzzbyf:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 16 Jan 2019 19:55:41 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>