-
Notifications
You must be signed in to change notification settings - Fork 250
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
General: Add package.json to each plugin #3072
Comments
Hey @oliverfoster is this issue still available |
Yes it is. 👍 |
Hey @oliverfoster , would it work to simply rename each bower.json file to a package.json? |
Nono, we need both files at the same time for the moment. Effectively the framework needs to be functional and up-to-date with minimal effort, and allow the npm architecture to be built around it for a smooth transition later. So no forking/branches/breaks but at the cost of some duplication. |
Hey @oliverfoster I think the link for adapt-contrib-core is broken. It directed me to a 404 page |
It hasn't been created yet. I'll talk it through with the team on their Monday meeting. I effectively need to move src/core into it's own adapt-contrib-core and link it back into the current src/core folder. |
Hey @oliverfoster , I am done. Let me know when |
superb, thankyou! |
No problem |
adapt-contrib-core is ready, I have added a package.json in the work already. Thank you for doing the others, it was a great help. |
Tasks
Plugins
The text was updated successfully, but these errors were encountered: