npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@talend/scripts-core

v16.5.1

Published

Set of scripts

Downloads

4,844

Readme

Talend Scripts

Description

This project, inspired by react-scripts and kcd-scripts, aims to abstract all tools and configuration from your project.

It will expose basic scripts:

  • start
  • test
  • build
  • lint
  • lint-merge-report

By default no configuration is needed (except for lint-merge-report) but you can at any time create a configuration file and extends from the default config.

talend-scripts will detect the kind of package you are in.

  • app: if you have src/app folder
  • lib: if not an app
  • angular: if there is a dependencies on angularjs
  • public project: you have a publishConfig: { access : 'public' } in your package.json

Depending on this the sub command will use a real command like webpack and apply either custom configuration or default configuration.

| command | app | lib | angular | | ------- | ------------------ | ------------------ | ------- | | build | webpack | babel | | | lint | eslint + stylelint | eslint + stylelint | | | test | jest | jest | karma | | start | webpack | start-storybook | |

Table of content

Basic usage

  1. Getting started

Advanced

  1. config customisation

Possible issues

Build

While building a huge app, you can run into a JavaScript heap out of memory, espacially on production mode, with webpack optimisation and sourcemap. You can increase the node space size to overcome this issue.

Package.json

{
	"scripts": {
		"build": "NODE_OPTIONS=--max_old_space_size=4096 talend-scripts build"
	}
}

Test

@talend/scripts-core uses jest to run tests. On mac and watch mode, if you have a lot of files to watch, you can bump into this error

$ jest --watch
2016-09-22 10:49 node[79167] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-22 10:49 node[79167] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-22 10:49 node[79167] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: Error watching file for changes: EMFILE
    at exports._errnoException (util.js:1036:11)
    at FSEvent.FSWatcher._handle.onchange (fs.js:1406:11)

The issue is well known, still not fixed in the lib or any of its dependencies. This github issue brings you a lot of info.

As a workaround, consider installing watchman.

brew install watchman

Extra scripts

We have added two scripts to be as simple as possible