Releases: Thom1729/Sublime-JS-Custom
Releases · Thom1729/Sublime-JS-Custom
v1.0.17
v1.0.16
- Add a new
scope
extension. By default, custom syntaxes will use ascope
ofsource.js.<name>
, where<name>
is the name of the configuration, lowercased, restricted to word characters and hyphens. The~embed
configuration (created in v1.0.15) has a default scope ofsource.js
, so other syntaxes should use~embed
instead of your other custom syntaxes when embedding thesource.js
scope. This should eliminate any remainingwith_prototype
recursion issues. (I hope that's the last time I type that sentence.) - Use
OutputPanel
from sublime_lib.
v1.0.15: Merge pull request #34 from Thom1729/embed-syntax
Adds a new builtin ~embed
configuration that disables custom_template_tags
. Fixes #17.
v1.0.14
v1.0.13
Use the latest upstream JavaScript syntax.
Incorporates improvements from the latest version of the core JavaScript syntax.
- Refactored statements, fixing bugs with comma operators and
for of
loops. - Improved parsing of class inheritance names.
- Implemented decorators.
- Implemented
import.meta
. - Added
begin
/end
to punctuation scopes. - Fixed bugs with method parsing.
Because decorators are now implemented in the core syntax, the es_decorators
option has been removed.
New extensions
Added the following new extensions:
es_pipeline
es_slice
hidden
v1.0.12
Integrated the following upstream changes:
- Improved function parameter bindings.*
- Support
new.target
. - Improved handling of tagged template strings.
- Improved identifier and number lexing.
- Fixed a bug with arrow function fallthrough.
- Allow arbitrary expressions in object rest spread.*
- Fixed a corner case when parsing function arguments.
- Un-nested some contexts.
* These changes had previously been patched into JS Custom directly. With those patches gone, the base syntax used by JS Custom is once again an exact copy of the core JavaScript syntax.
Also:
- Fixed a Flow bug in which types beginning with keywords would be parsed wrong.
- Made some extensions more granular as a result of upstream refactoring, cutting code.
v1.0.11
v1.0.10
v1.0.9
Hide Styled Components
The Styled Components syntax is only used to support the styled_components
configuration option. It should be hidden from menus and so forth.