Skip to content

Releases: Js-Brecht/gatsby-plugin-ts-config

v2.1.0

04 Sep 23:11
Compare
Choose a tag to compare
  • Integrates a "base" transpiler, allowing the transpiler to stay on after hitting the gatsby-* files it can find.

    • This will allow plugins that use .ts files to still be transpiled by Gatsby itself
    • The first settings defined for the transpiler will be the settings used by the base transpiler
  • Added ignore hooks. Information is in the README.md, in the options documentation

v2.0.2

04 Sep 03:22
Compare
Choose a tag to compare
  • Fix module resolution when .ts file is next to its .js, and extension isn't explicitly defined.

v2.0.1

26 Aug 06:02
Compare
Choose a tag to compare
  • Fix transpiler require path resolution

Major version 2.0 release

15 Aug 08:47
481c697
Compare
Choose a tag to compare
  • Removes the "proxy" method for providing Typescript gatsby-config and gatsby-node content to Gatsby

    Instead of proxying via the Gatsby Theme method, gatsby-config.js and/or gatsby-node.js will call useGatsbyConfig or useGatsbyNode, respectively, to transpile and pass their respective content to Gatsby

Breaking changes

Type changes

  • IGatsbyPluginDef -> GatsbyPlugin
  • ITSConfigFn -> TSConfigFn
  • Second parameter on TSConfigFn (PropertyBag types) changed
    • If you were using an interface to define your property bag, it should be changed to a type, or you may get errors about it needing a string index

Plugin API

  • generateConfig replaced by useGatsbyConfig and useGatsbyNode
  • Plugin options changed, see: https://github.com/Js-Brecht/gatsby-plugin-ts-config#options
    • Dropped babel and tsNode; replaced with type and transpilerOptions
  • Dropped properties on default export function parameters
    • endpoints (now imports)
    • configDir
    • cacheDir
  • Property bag definition is no longer the second parameter of the bootstrap functions
    • It is included in plugin options as the props key

Project structure

  • gatsby-browser and gatsby-ssr are no longer proxied; they must be in your site's root directory
  • gatsby-node is no longer proxied; it must have a module in your site's root directory

v1.1.6

07 Aug 03:50
Compare
Choose a tag to compare
  • Allows boolean false values in the plugin list, and filters them out before passing to Gatsby.

v1.1.5

08 Dec 18:16
Compare
Choose a tag to compare
  • Appends /package.json to the resolved plugin paths, to make Gatsby's plugin directory resolution more definitive.

v1.1.3

25 Nov 01:08
Compare
Choose a tag to compare
  • Makes props parameter of generateConfig() optional
  • Adds allExtensions: true to *.tsx babel preset

v1.1.1

31 Oct 02:44
Compare
Choose a tag to compare
  • Removes the property bag in onPreInit, so that it doesn't get passed to the browser.

v1.1.0: Dynamic Property Bag

10 Oct 02:26
Compare
Choose a tag to compare
  • Implements a dynamic property bag (#19)
  • Upgrades ts-node to v9.0.0 for compatibility with transformers

v1.0.0: Local Plugin Resolver

11 Aug 19:23
Compare
Choose a tag to compare
  • Adds functionality for resolving (and compiling) local plugins.
  • Adds functionality for resolving all plugin paths before they get to Gatsby, so that it can use plugins via proxy.