Skip to content

0.5.x Work in Progress #194

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

Merged
merged 244 commits into from
Jan 25, 2018
Merged

0.5.x Work in Progress #194

merged 244 commits into from
Jan 25, 2018

Conversation

davidlehn
Copy link
Member

@davidlehn davidlehn commented Jul 26, 2017

DO NOT MERGE: This is a work-in-progress PR tracking 0.5.x progress.

While under development the 0.5.x branch is being published to npm with the "dev" tag. 0.4.x will use the "latest" tag until 0.5.x is mature.
NOTE: This branch has been released as the "latest" npm tag as 0.5.17.

A main 0.5.x feature will be switching to a more modular system based on CommonJS and ES2015. Modularity was also done in #126. That effort went fully to ES modules. This attempt will likely start using CommonJS and have more functionality per file. As was done in the forge update, CommonJS is used for Node.js compatibility and webpack (or similar) will be used to create browser bundles.

  • Remove AMD/etc boilerplate.
  • Adadpt CommonJS style.
  • Top level options (as in forge) for native code control. jsonld.options.usePureJavaScript Used for at least allowing native SHA256 implementation.
  • webpack built browser bundles and testing. Set up to allow building custom bundles with just needed functionality. Aim towards future ES module design.
  • Browserify built bundles and testing.
  • Add docs on various tools and methods to create custom bundles
  • Testing: Node.js
  • Testing: In a browser manually via a webpack build of all tests
  • Testing: PhantomJS, Chrome, Firefox, and Safari via Karma (webpack version)
  • Testing: PhantomJS, Chrome, Firefox, and Safari via Karma (browserify version)
  • Testing: Travis-CI passing Node.js and PhantomJS tests
  • Docs updated
  • Style and misc cleanups
  • Drop Bower support? It's deprecated in favor of NPM. Much easier to only support built minimized bundles in NPM releases and magic NPM CDN hosting. Alternate is to do as forge does with secondary repo and complex release process. Make sure not to break bower usage (tags, etc).
  • Update local testing.
  • Improve support for local tests.
  • Remove as much old build/test cruft as possible.
  • Add some (not too slow) nodejs and web tests with jsonld.options.usePureJavaScript===true.
  • webpack vs node/browserify test count.
  • Check npm pack.
  • .editorconfig
  • 0.5.0 Milestone Issues

As this is a rather major change it needs testing and feedback before hitting master. Please test and leave comments, thanks!

@davidlehn davidlehn self-assigned this Jul 26, 2017
@davidlehn davidlehn added this to the v0.5.0 milestone Jul 26, 2017
mattcollier and others added 16 commits July 26, 2017 12:21
Removed:
- Bower support. Use NPM, a NPM proxy site, or build your own bundle.

Changed:
- Switch to Karma for browser testing.
- Switch to webpack to build browser bundles.
- Use async APIs for test generation.
  - Done to allow testing in Node.js and browsers.
  - Required major testing changes to make everything async.
  - Workarounds added to get async generated mocha tests working.
- Improved support for loading various types of tests.
  - Can load local files, test manifests, or plain js files (in Node.js).
- Use ES2015 in tests and babel/webpack to support older platforms.
- Add package files.
- Add prepublish script.
- Fixes.
Karma config has it's own webpack rules.
- Add done call.
- Add to node tests.
- Remove Makefile.
- Add scripts directly in package.json.
- Add fetch-test-suites script to create shallow copies.
- Update travis support to use fetch-test-suites.
- Update README.
- Default to local ./test-suites/ else sibling dirs.
gkellogg and others added 28 commits January 9, 2018 13:03
- Use array representation of @container in processing.
- Improved error detection for @container variations.
…, `@id`, `@language`, `@reverse`, and `@type`. This also sets up for additional keywords in 1.1.
…venting cases when keyword alias had `@type` defined, as in Compact 0073.
@davidlehn davidlehn merged commit 8d036d8 into master Jan 25, 2018
@davidlehn
Copy link
Member Author

This branch has been merged into master and released as npm "latest". Remaining items above will be added as issues and addressed in 0.5.x, 0.6.x, or later as appropriate.

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

Successfully merging this pull request may close these issues.

6 participants