Unit tests need to be run through webpack so we can run tests on the debugger and production versions. Also opens up the possibility of adding ES2015+ features to tungsten.js core.

To avoid issues like the one solved by #111.

Highlight patterns and anti-patterns, etc.

Using objects with hook and unhook functions to process values during patch options. Should open the door to better input focus support and animation support.

Provide an abstraction layer where we output virtual dom so that we can swap out the DOM updating libraries, potentially with something like incremental DOM.

Probably use prePublish in npm scripts.

Prepublish script to publish only the dist modules.

Testing

We should be able to replace all the important functionality of jscs and jsbeautify with eslint, and it would probably be helpful to have the rules consolidated into one library.

Create some basic functional tests for the example apps

Implement declarative API for expressing canvas via templates. Needs to be ignored on server side rendering.

Add ability to nest components with their own view/model/template within existing Tungsten.js applications.

What the title says :)

Provide an interface for swapping out the source template type so that you can build tungstenjs with support for other template libraries, such as handlebars or jade.

Move backbone adaptor and ampersand adaptor to their own npm modules so that initial installs don't download unnecessary dependencies, especially as the number of adaptors increases.

See tests at b6e4946. The first one passes, the second one fails. Seems to be a bug in Ractive, but we may be able to fix it on our end.

Overview

Let's make some progress with the @todo: automate more of this process in gh_pages/readme.md.

We'll create the ability to run the command npm run build-and-deploy.

This will replace the two steps in gh_pages/readme.md that read: npm run build and # replace 'gh-pages' branch content with the built site directory.

Possible Implementation

I suggest we use a basic script along the lines of this one to create a local copy of the gh-pages branch. We'll clear it of old content, copy in the new content, and add a commit with the SHA that the master branch was at when we regenerated. Then we'll push gh-pages up.

Finally, we'll update the documentation.

In the tutorial, ctrl+enter doesn't run the code, it's shift+enter that does the trick.

With documentation and hosted example apps

Currently the examples don't implement filters or routing. Add this functionality to match up with the spec.

Document what's necessary to implement a custom adaptor with a view/model library.

Quick fix in #65, but need to find root cause

Hi there,

We noticed that your repo has a low severity vulnerability:

• Regular Expression Denial of Service
• Affected package: ms <=0.7.0

Here is the test report for this repo.
If you’d like to fix this vulnerability, Snyk lets you generate a pull request that recommends the best upgrade path - there’s a link to fix this vulnerability on the test report.

Stay secure :-)
Snyk Community

Host and link to the built example apps on our ghpages

• optimize loops / logic, e.g. defaultEventHandler
• work on TODO

I'm currently looking into perf issues with scrolling and noticed that there's room for optimization.

Readme is starting to get a bit too long. Break it up into individual md files in a ./docs folder.

Implement fix for transferring listeners (#90) to Ampersand adaptor, with tests.

Add documentation to readme for: https://github.com/wayfair/tungstenjs/blob/master/adaptors/backbone/base_view.js#L435

There are some undocumented restrictions on how templates need to be written (e.g., with conditionals in element attributes). Add notes in readme.

More detail is needed on the easiest way to get started with a new tungsten.js project using webpack (e.g., using the webpack-helper module).

So that you can easily check which version is being used

What I'm trying to do

Install the tungstenjs and use the tungsten_template webpack loader from within the tungstenjs installation, as outlined in the project's documentation.

Expected result

Webpack is able to look up tungsten_template from the node_modules/tungstenjs/precompile directory

Actual result

The precompile directory is not present in the installation's directory. Only dist is available below the top level.

Steps to reproduce

$ mkdir tungsten-install-test && cd tungsten-install-test
$ npm init --yes
$ npm install --save tungstenjs
$ ls node_modules/tungstenjs

Something that stands out in the installed package.json within tungsten's install directory is that the files property looks like

{
  // ...
  "files": [
    "dist"
  ],
  // ...
}

but I can't seem to figure out what configuration is causing this. Please let me know if more information is needed!