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

stt-data

v0.0.26

Published

Data definition and access for Smart Tourism Transition

Downloads

29

Readme

Using this package

Setup your environment

You can customize the environment in which services are run by updating the axios instance's defaults. Do that before anything in your code (after the imports in src/index.js if you use React/CRA) :

src/index.ts

import React from 'react';
import ReactDOM from 'react-dom/client';
import { App } from './App';
import { configure } from 'stt-data';

configure({
  baseURL: process.env.REACT_APP_API_URL,
  withCredentials: true,
  headers: {
    appId: process.env.REACT_APP_APP_ID,
    appPassword: process.env.REACT_APP_APP_PASSWORD
  }
});

const root = ReactDOM.createRoot(document.getElementById('root'));
root.render(<App />);

// ...

Consume the services

src/App.tsx

import { useState, useEffect } from 'react';
import { createUser, getUsers, User, UserInput } from 'stt-data';

export const App = () => {
  const [newUserProps, setNewUserProps] = useState<UserInput>({firstName: '', lastName: ''})
  const handleFormSubmit = () => createUser(newUserProps)

  const [users, setUsers] = useState<UserInput>([])
  useEffect(() => {
    getUsers().then(setUsers)
  }, []);

  return (
    // ...
  );
};

Making your client compliant to the latest version of STT API

npm i stt-data@latest

If you use TS, and the API has a breaking change, you will direclty know what are the portions of your code to apdapt. 👍

Developing this package

Starting

npm i

Scafolding

# Usage
npm run generateCRUD <entityName> <attributes>
# Examples
npm run generateCRUD Article "title:string body:string published:boolean mainPictureUrl?:string"
npm run generateCRUD Unicorn "name:string age:number"

Editing

If you use the CRUD generator, always check that what was generated is correct :)

Also, please follow those rules :

  • never use default exports
  • never create "index.ts" files yourself (they will be generated automatically when commiting or before publication)

Publishing

Ready to publish some updates of the API ?

npm run <update_type>

Just replace <update_type> by patch, major or minor following semver.