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

Requirements? #11

Closed
BigBlueHat opened this issue Aug 23, 2017 · 1 comment
Closed

Requirements? #11

BigBlueHat opened this issue Aug 23, 2017 · 1 comment
Assignees

Comments

@BigBlueHat
Copy link
Member

I just successfully ran the demo with node 7.10.0 and npm 4.2.0

However, I've not yet attempted the hot-reload stuff.

@tilgovi are there specific things that node 8 and npm 5 enable that I'm missing?

@tilgovi
Copy link
Contributor

tilgovi commented Aug 24, 2017

I just didn't want to moderate my use of ES2017. The only script is bin/start.mjs, though, which is pretty simple.

I'll address this issue as soon as I can. Probably, I should re-introduce babel into the pipeline and formalize the build targets and developer runtime requirements.

tilgovi added a commit that referenced this issue Aug 24, 2017
Add babel to the development tools again. A new compatibility directory
contains a small shim that takes the place of @std/esm on command line
invocations. This shim installs babel-polyfill to modernize the
environment globals, babel-register to transpile advanced syntax and
language features, and @std/esm to provide spec-compliant module
semantics.

With babel back in the toolchain, update the demo webpack configuration
to support recent versions of the major browsers.

Close #11
tilgovi added a commit that referenced this issue Aug 24, 2017
Add babel to the development tools again. A new compatibility directory
contains a small shim that takes the place of @std/esm on command line
invocations. This shim installs babel-polyfill to modernize the
environment globals, babel-register to transpile advanced syntax and
language features, and @std/esm to provide spec-compliant module
semantics.

With babel back in the toolchain, update the demo webpack configuration
to support recent versions of the major browsers.

Close #11
tilgovi added a commit that referenced this issue Aug 25, 2017
Add babel to the development tools again. A new compatibility directory
contains a small shim that takes the place of @std/esm on command line
invocations. This shim installs core-js to modernize the environment
globals and loads @std/esm to enable module features.

Update the demo webpack configuration to use babel-loader and target
recent versions of major browsers.

Add babel-eslint so that eslint can parse new syntax. It is not enabled
at the root because the build tools use @std/esm but not babel. For the
build scripts, core-js polyfills new globals but new syntax is
disallowed. For the browser, syntax that has not reached stage 3 of the
TC39 process is explicitly restricted because babel-eslint does not
accept any preset configuration.

With these changes, stage 3 polyfills should be supported in the
toolchain and the packages and stage 3 syntax should be supported in the
packages. Linting should accurately reflect this support.

Close #11
tilgovi added a commit that referenced this issue Aug 25, 2017
Ensure that the build system works under Node 4.

- Configure ESLint for ES6 and disable parser support for new syntax.

Target recent browsers and stage 3 ECMAScript proposals for packages.

- Configure ESLint for ES2017 support

- Add babel, babel-loader and babel-eslint

- Restrict syntax forms that have not reached stage 3, since
  babel-eslint cannot be otherwise configured

Close #11
tilgovi added a commit that referenced this issue Aug 25, 2017
Ensure that the build system works under Node 4.

- Configure ESLint for ES6 and disable parser support for new syntax.

Target recent browsers and stage 3 ECMAScript proposals for packages.

- Configure ESLint for ES2017 support

- Add babel, babel-loader and babel-eslint

- Restrict syntax forms that have not reached stage 3, since
  babel-eslint cannot be otherwise configured

Close #11
tilgovi added a commit that referenced this issue Aug 25, 2017
Ensure that the build system works under Node 4.

- Configure ESLint for ES6 and disable parser support for new syntax.

Target recent browsers and stage 3 ECMAScript proposals for packages.

- Configure ESLint for ES2017 support

- Add babel, babel-loader and babel-eslint

- Restrict syntax forms that have not reached stage 3, since
  babel-eslint cannot be otherwise configured

Close #11
tilgovi added a commit that referenced this issue Aug 25, 2017
Ensure that the build system works under Node 4.

- Configure ESLint for ES6 and disable parser support for new syntax.

Target recent browsers and stage 3 ECMAScript proposals for packages.

- Configure ESLint for ES2017 support

- Add babel, babel-loader and babel-eslint

- Restrict syntax forms that have not reached stage 3, since
  babel-eslint cannot be otherwise configured

Close #11
tilgovi added a commit that referenced this issue Aug 25, 2017
Ensure that the build system works under Node 4.

- Configure ESLint for ES6 and disable parser support for new syntax.

Target recent browsers and stage 3 ECMAScript proposals for packages.

- Configure ESLint for ES2017 support

- Add babel, babel-loader and babel-eslint

- Restrict syntax forms that have not reached stage 3, since
  babel-eslint cannot be otherwise configured

Close #11
tilgovi added a commit that referenced this issue Aug 25, 2017
Ensure that the build system works under Node 4.

- Configure ESLint for ES6 and disable parser support for new syntax.

Target recent browsers and stage 3 ECMAScript proposals for packages.

- Configure ESLint for ES2017 support

- Add babel, babel-loader and babel-eslint

- Restrict syntax forms that have not reached stage 3, since
  babel-eslint cannot be otherwise configured

Close #11
tilgovi added a commit that referenced this issue Aug 25, 2017
Ensure that the build system works under Node 6.

- Configure ESLint for ES6 and disable parser support for new syntax.

Target recent browsers and stage 3 ECMAScript proposals for packages.

- Configure ESLint for ES2017 support

- Add babel, babel-loader and babel-eslint

- Restrict syntax forms that have not reached stage 3, since
  babel-eslint cannot be otherwise configured

Close #11
tilgovi added a commit that referenced this issue Aug 25, 2017
Ensure that the build system works under Node 6.

- Configure ESLint for ES6 and disable parser support for new syntax.

Target recent browsers and stage 3 ECMAScript proposals for packages.

- Configure ESLint for ES2017 support

- Add babel, babel-loader and babel-eslint

- Restrict syntax forms that have not reached stage 3, since
  babel-eslint cannot be otherwise configured

Close #11
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

2 participants