afterwriting / aw-parser Goto Github PK

View Code? Open in Web Editor NEW

4.0 4.0 1.0 102 KB

Fountain parser

License: MIT License

JavaScript 87.18% HTML 9.55% CSS 0.57% Shell 2.70%

fountain parser screenwriting

aw-parser's People

Contributors

Stargazers

Watchers

Forkers

sdgxdx

aw-parser's Issues

Allow multiple empty lines

ifrost/afterwriting-labs#67

Transition overrides forced scene heading

ifrost/afterwriting-labs#86

An in-range update of webpack is breaking the build 🚨

Version 4.16.4 of webpack was just published.

Branch	Build failing 🚨
Dependency	webpack
Current Version	4.16.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes

v4.16.4

Bugfixes

fix chunkAsset hook in HotModuleReplacementPlugin

Commits

The new version differs by 15 commits.

1e9d98c 4.16.4
e163495 Merge pull request #7838 from webpack/test/jest-exported-tests
01cfe5b improve way of adding exported tests to test tree
5f1852a Merge pull request #7831 from EECOLOR/patch-1
afe3182 Merge pull request #7836 from rzhe97/master
c893bbc Update CONTRIBUTING.md
2348c3c Formatting - move arguments to the same line
7473ed4 Fix chunkAsset hook call
32fdca2 Merge pull request #7823 from flyyang/refactor/define-before-use-class
e4ae646 Merge pull request #7825 from webpack/deps/update_linters
64e301c Update Prettier
20406a4 Update ESLint
5234abe Refactor define before use class
61ce434 Merge pull request #7819 from webpack/refactor/template_es6
3992ba3 Convert Template to ES6

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of sinon is breaking the build 🚨

Version 4.1.6 of sinon was just published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	4.1.5
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details