archive/rsnext

Fork 0

Commit graph

Author	SHA1	Message	Date
Kristoffer K	104b8d4732	fix(next-mdx): resolve webpack loader (#17983 ) What's the problem this PR addresses? `@next/mdx` adds the webpack loader `@mdx-js/loader` without resolving it to an absolute path Depends on https://github.com/vercel/next.js/pull/17606 How did you fix it? `require.resolve` the webpack loader before adding it	2021-01-04 16:24:16 +00:00
Joe Haddad	18a9c7e371	Improve linting rules to catch more errors (#9374 ) * Update `packages/` * Update examples * Update tests * Update bench * Update top level files * Fix build * trigger	2019-11-10 19:24:53 -08:00
JJ Kasper	491f9a2c49	Move next-mdx from zeit/next-plugins to zeit/next.js (#6443 ) At request of @timneutkens I moved the `next-mdx` plugin from the next-plugins repo into Next.js. Also fixed small typo in README under setup.	2019-03-04 18:02:45 +01:00

Author

SHA1

Message

Date

Kristoffer K

104b8d4732

fix(next-mdx): resolve webpack loader (#17983 )

**What's the problem this PR addresses?**

`@next/mdx` adds the webpack loader `@mdx-js/loader` without resolving it to an absolute path

Depends on https://github.com/vercel/next.js/pull/17606

**How did you fix it?**

`require.resolve` the webpack loader before adding it

2021-01-04 16:24:16 +00:00

Joe Haddad

18a9c7e371

Improve linting rules to catch more errors (#9374 )

* Update `packages/`

* Update examples

* Update tests

* Update bench

* Update top level files

* Fix build

* trigger

2019-11-10 19:24:53 -08:00

JJ Kasper

491f9a2c49

Move next-mdx from zeit/next-plugins to zeit/next.js (#6443 )

At request of @timneutkens I moved the `next-mdx` plugin from the next-plugins repo into Next.js. Also fixed small typo in README under setup.

2019-03-04 18:02:45 +01:00

3 commits