next.js

terribleplan/next.js

Fork 0

mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00

Commit graph

Author	SHA1	Message	Date
Henrik Wenz	18488f47b0	Fix linter (#5350 ) * Fix linter * Add test env * Fix lint errors	2018-10-20 17:00:01 +02:00
Tim Neutkens	17e410a1d0	Fix Typescript HMR (#4689 ) Fixes #4686 Adds tests for @zeit/next-typescript so that we don't regress on this again. I've fixed an issue in the `next` CLI too which caused lingering processes when the process gets force killed, which is what we do in the test suite, so it kept running if there was no manual quit.	2018-06-28 20:07:41 +02:00
Logan Smyth	2495316235	Use custom Babel loader to avoid using separate Babel copies for loader and loader options (#4417 ) This resolves the > .value is not a valid Plugin property error showing up for people in https://github.com/zeit/next.js/issues/4227 cc @timneutkens	2018-05-23 20:26:57 +02:00

Author

SHA1

Message

Date

Henrik Wenz

18488f47b0

Fix linter (#5350 )

* Fix linter

* Add test env

* Fix lint errors

2018-10-20 17:00:01 +02:00

Tim Neutkens

17e410a1d0

Fix Typescript HMR (#4689 )

Fixes #4686

Adds tests for @zeit/next-typescript so that we don't regress on this again.

I've fixed an issue in the `next` CLI too which caused lingering processes when the process gets force killed, which is what we do in the test suite, so it kept running if there was no manual quit.

2018-06-28 20:07:41 +02:00

Logan Smyth

2495316235

Use custom Babel loader to avoid using separate Babel copies for loader and loader options (#4417 )

This resolves the

> .value is not a valid Plugin property

error showing up for people in https://github.com/zeit/next.js/issues/4227

cc @timneutkens

2018-05-23 20:26:57 +02:00

3 commits