Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@taal-enterprise/shared-components
Advanced tools
This repo is the taal shared component library released as an npm package.
This repo is the taal shared component library released as an npm package.
yarn
You can visualise the shared components by running storybook:
yarn storybook
Starting from version v4.0.0 all apps must use SharedThemeProvider
to wrap whole app.
<SharedThemeProvider appTheme={localThemeGoesHere}>
<App />
</SharedThemeProvider>
or look at https://bitbucket.org/Taal_Orchestrator/taal-console/src/main/src/components/base/app-provider.js
Its useful to test to see if the library is working correctly without having to publish. The following are instructions on how to do to this in a Next.js project:
"main": "src/index.js",
"module": "src/index.js",
yarn link
in the root of this projectyarn add -D next-transpile-modules
in the consuming project if this package is not already installed.yarn link @taal-enterprise/shared-components
in the consuming project.const path= require("path")
const withTM = require('next-transpile-modules')(['@taal-enterprise/shared-components'], {
resolveSymlinks: false,
debug: true,
});
module.exports = withTM({
// ...
eslint: {
ignoreDuringBuilds: true,
},
webpack: (config, options) => {
config.resolve.alias['styled-components'] = path.resolve('./node_modules/styled-components')
config.resolve.alias.react = path.resolve('./node_modules/react')
config.resolve.alias['react-dom'] = path.resolve('./node_modules/react-dom')
config.resolve.alias['react-hook-form'] = path.resolve('./node_modules/react-hook-form')
//See the following issue for the reason for setting the polling
//https://github.com/martpie/next-transpile-modules/issues/236#issuecomment-926583362
if (process.env.NODE_ENV === 'development') {
config.watchOptions = {
poll: 2500,
};
}
return config
}
});
As we add more peer dependancies this will need to be updated. More details on why the above is needed can be found here
yarn unlink
command and in the consuming project run yarn link @taal-enterprise/shared-components
.For more on npm link and how it works click here
yarn build
to create the bundled library.npm login
(You should already a npm account and have permison to publish the package)npm run release -- --message='DEVP-<number>: <comment>'
For more details on using np click here
FAQs
This repo is the taal shared component library released as an npm package.
The npm package @taal-enterprise/shared-components receives a total of 0 weekly downloads. As such, @taal-enterprise/shared-components popularity was classified as not popular.
We found that @taal-enterprise/shared-components demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.