-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extensions and themes splited into node packages #899
Conversation
52c531d
to
f0548fe
Compare
643eab4
to
03d5baf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me it's good. Can be merged to develop. I've tested it Yesterday, everything works just fine
core/app.js
Outdated
@@ -46,7 +45,15 @@ export function createApp () { | |||
render: h => h(App) | |||
}) | |||
|
|||
registerExtensions(_.union(extensionEntryPoints, config.requiredExtensions) || [], app, router, store, config) // TODO: use config or ENV variables | |||
// TODO: use config or ENV variables |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pkarw do you know if this TODO is still necessary here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't remember what did I mean by this :) remove it :)
I Will test tomorrow on Windows and Linux |
Works for me on Windows/ElementaryOS, merging ;) |
Tested on Windows 10 and works great on except v-viewer has stopped working. It was working but now seems to be hung up with SSR type problems after yarn. I verified the version didn't change so I'm not quite sure what's up with that. |
@jimcreate78 Could you create a new issue with some scenario to reproduce it? |
I will try and stage the issue |
I dropped support of
npm
for core development, b/c onlyyarn
support workspaces (apart of other advantages)All hacks related to manually running
npm
in the child folders are removed, b/c are not necessary anymore.I also introduced some very basic packages naming convention:
@vue-storefront
is the official namespace@vue-storefront/theme-*
is for themes@vue-storefront/extension-*
is for extensionsPackages, for now, are not published.
The whole process of splitting the codebase is not done yet, the core is still waiting.
I'm creating this PR mostly to test everything on few machines, before merging anything.