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
[META] Where do our libraries live? #8
Comments
Started refactoring these into npm package.json files. the node_modules layout is a little bit different than what we have put into our repo and I am not sure which packages to reference on a few. We'll talk about this on Tuesday (training all day Monday). See my branch 'features/markie/8-packaging' |
and then there's this: https://www.drupal.org/developing/api/8/assets#external
|
Can you PR your branch with progress on this just so we can see the diff? |
PR: #18 for your mocking goodness. |
On further consideration I think loading externally in our libraries might be the perfect way to handle this, at least for our POC. It will allow us to keep the libraries out of the filesystem without adding additional dependencies. In any case, the PR above needs latest merged into it. |
This can probably be closed per PR: #31 or we can continue the discussion. Both the react and NG2 libraries load from the externals. |
For pdb_ng2 at least, I've accepted the value in an npm dependency (both the upgrade to RC1 and the latest developments on #52 pushed me in this direction). As such, I've moved most of the library sources to use node_module locations. Ultimately I think where our libraries live will be a framework-level decision, for which individual tickets can be opened. Closing this. |
As of this moment, React and Angular 2 are both included in our code base, inside their framework sub-modules under assets/vendor directories.
This is unsustainable for multiple reasons, and we need to figure out how these libraries will be included in projects.
The text was updated successfully, but these errors were encountered: