Skip to content
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

Investigate sym-linking depedencies #633

Closed
marcoscaceres opened this issue Mar 10, 2016 · 2 comments
Closed

Investigate sym-linking depedencies #633

marcoscaceres opened this issue Mar 10, 2016 · 2 comments

Comments

@marcoscaceres
Copy link
Member

According to the require RequireJS docs, it might be cleaner to have dependencies in a "js/lib" folder, and then load them relative. Might be worth looking into.

@marcoscaceres
Copy link
Member Author

It turns out to be messy

@marcoscaceres
Copy link
Member Author

Been reading more into this. It's actually a good thing if we transition to browserify.

marcoscaceres pushed a commit that referenced this issue Jun 21, 2016
chore(deps): move dependencies to js/deps (closes #633)
marcoscaceres added a commit that referenced this issue Jun 24, 2016
* develop:
  v3.3.3
  chore(package): update karma to version 1.0.0
  chore(package): update snyk to version 1.16.0
  fix: package.json & .snyk to reduce vulnerabilities
  chore(utils): fix style
  chore(package): update jscs to version 3.0.5
  chore(package): update jasmine-reporters to version 2.2.0
  chore(deps): move dependencies to js/deps (closes #633)
  chore(markdown): tell hljs about xquery+http+markdown
  Feat(package): adds xquery to highlight build
  Feat(highlight): build custom highlighter
  Fix(biblio): use herokuapp instead of w3c proxy
  chore(CHANGELOG): generate changelog for 3.3.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant