You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, is there a support to serve multiple version of an npm component package?
E.g.: I have a components library of v1.0 but there will be major changes in v2.0 that would break the earlier pages made with v1.0, is there an ability to provide multiple versions of that package and serve by some version property?
is there a way to provide it with different versions?
(inserting proper version into _Layout.cshtml doesn't seem like a problem, neither installing different version with npm alias and/or outputting to dist folders with version)
Thanks
The text was updated successfully, but these errors were encountered:
I think webpack has support for this via aliases. Your entry point would be
something like
module.exports = {
ComponentV1 = require(‘componentv1’),
ComponentV2 = require(‘componentv2’)
}
I don’t remember offhand what webpack config changes are needed to make it
work.
Oh so I would have several entry points and outputs with versions and use the app.UseReact with just the ~dist folder with all the versions and just include them in the layout. so it would be only about setting the webpack right?
Hi, is there a support to serve multiple version of an npm component package?
E.g.: I have a components library of v1.0 but there will be major changes in v2.0 that would break the earlier pages made with v1.0, is there an ability to provide multiple versions of that package and serve by some version property?
the scripts are added in the startup:
is there a way to provide it with different versions?
(inserting proper version into _Layout.cshtml doesn't seem like a problem, neither installing different version with npm alias and/or outputting to dist folders with version)
Thanks
The text was updated successfully, but these errors were encountered: