backstage/plugins/search-backend-node/CHANGELOG.md

@backstage/plugin-search-backend-node

0.2.2

Patch Changes

• 9c8ea7e24: Handle errors in collators and decorators and log them.
• 7e7cec86a: Fixed bug preventing searches with filter values containing : from returning results.

0.2.1

Patch Changes

• 14aad6113: Improved the quality of free text searches in LunrSearchEngine.

0.2.0

Minor Changes

• 5aff84759: This release represents a move out of a pre-alpha phase of the Backstage Search plugin, into an alpha phase. With this release, you gain more control over the layout of your search page on the frontend, as well as the ability to extend search on the backend to encompass everything Backstage users may want to find.

  If you are updating to version v0.4.0 of @backstage/plugin-search from a prior release, you will need to make modifications to your app backend.

  First, navigate to your backend package and install the two related search backend packages:

  cd packages/backend
  yarn add @backstage/plugin-search-backend @backstage/plugin-search-backend-node
  

  Wire up these new packages into your app backend by first creating a new search.ts file at src/plugins/search.ts with contents like the following:

  import { useHotCleanup } from '@backstage/backend-common';
  import { createRouter } from '@backstage/plugin-search-backend';
  import {
    IndexBuilder,
    LunrSearchEngine,
  } from '@backstage/plugin-search-backend-node';
  import { PluginEnvironment } from '../types';
  import { DefaultCatalogCollator } from '@backstage/plugin-catalog-backend';
  
  export default async function createPlugin({
    logger,
    discovery,
  }: PluginEnvironment) {
    // Initialize a connection to a search engine.
    const searchEngine = new LunrSearchEngine({ logger });
    const indexBuilder = new IndexBuilder({ logger, searchEngine });
  
    // Collators are responsible for gathering documents known to plugins. This
    // particular collator gathers entities from the software catalog.
    indexBuilder.addCollator({
      defaultRefreshIntervalSeconds: 600,
      collator: new DefaultCatalogCollator({ discovery }),
    });
  
    // The scheduler controls when documents are gathered from collators and sent
    // to the search engine for indexing.
    const { scheduler } = await indexBuilder.build();
  
    // A 3 second delay gives the backend server a chance to initialize before
    // any collators are executed, which may attempt requests against the API.
    setTimeout(() => scheduler.start(), 3000);
    useHotCleanup(module, () => scheduler.stop());
  
    return await createRouter({
      engine: indexBuilder.getSearchEngine(),
      logger,
    });
  }
  

  Then, ensure the search plugin you configured above is initialized by modifying your backend's index.ts file in the following ways:

  +import search from './plugins/search';
  // ...
  +const searchEnv = useHotMemoize(module, () => createEnv('search'));
  // ...
  +apiRouter.use('/search', await search(searchEnv));
  // ...
  

Patch Changes

• db1c8f93b: The `<Search...Next /> set of components exported by the Search Plugin are now updated to use the Search Backend API. These will be made available as the default non-"next" versions in a follow-up release.

  The interfaces for decorators and collators in the Search Backend have also seen minor, breaking revisions ahead of a general release. If you happen to be building on top of these interfaces, check and update your implementations accordingly. The APIs will be considered more stable in a follow-up release.

• Updated dependencies [db1c8f93b]

  • @backstage/search-common@0.1.2

0.1.4

Patch Changes

• e1e757569: Introduced Scheduler which is responsible for adding new tasks to a schedule together with it's interval timer as well as starting and stopping the scheduler processes.

0.1.3

Patch Changes

• b9b2b4b76: Lunr Search Engine support

0.1.2

Patch Changes

• 4d248725e: Bump to use the in-repo latest backend-common, and the correct version of express-promise-router