zcy
/
maxGraph
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
maxGraph/package.json

36 lines
991 B
JSON
Raw Permalink Normal View History

Added Gruntfile and package.json for npm install; updated .gitignore
2017-08-08 14:13:24 +00:00
{
Refactored everything...
2021-09-07 09:07:27 +00:00
"name": "maxgraph",
chore: improve the configuration to build the npm package (#87) Root and all package.json files - Fix license, version and authors - Remove the non-relevant .npmignore file at the project. It was designed for mxgraph, the whole directory structure changed, and we don't plan to publish the root package `core` package - Generate type definition and javascript files for ESM output - dedicated folder for `esm` and `types` in the `dist` folder to clearly separate concerns - exported in the package.json - Add npm script for `npm pack` configuration - Drop the `postinstall` npm script that built the `core` bundle. It would have been run when the package is installed in dependent projects at dependencies install. And it would have failed as it tries to build the project from TypeScript sources that are not available in the npm package. fix: ConstraintHandler now loads image as everywhere else in the code using `Client.imageBasePath` Using import doesn't work as the image is not available in the npm package. It generated error like this in ViteJS project: Failed to resolve import "../../../images/point.gif" from "../core/dist/esm/view/handler/ConstraintHandler.js". Does the file exist? This gif import had been introduced to make `Anchors.stories.js` retrieve the gif file. Configuring `imageBasePath` as already done in other stories fixes the issue. Don't export EditorCodec and StylesheetCodec as they generate errors. This is a temporary solution to avoid error in dependent project (at least, with ViteJS projects).
2022-07-05 06:08:25 +00:00
"license": "Apache-2.0",
chore: review private property in package.json files (#244) Remove versioning for private packages are they are not supposed to be consumed outside the project. Explicitly mark public packages.
2023-09-15 10:31:22 +00:00
"private": true,
chore: improve the configuration to build the npm package (#87) Root and all package.json files - Fix license, version and authors - Remove the non-relevant .npmignore file at the project. It was designed for mxgraph, the whole directory structure changed, and we don't plan to publish the root package `core` package - Generate type definition and javascript files for ESM output - dedicated folder for `esm` and `types` in the `dist` folder to clearly separate concerns - exported in the package.json - Add npm script for `npm pack` configuration - Drop the `postinstall` npm script that built the `core` bundle. It would have been run when the package is installed in dependent projects at dependencies install. And it would have failed as it tries to build the project from TypeScript sources that are not available in the npm package. fix: ConstraintHandler now loads image as everywhere else in the code using `Client.imageBasePath` Using import doesn't work as the image is not available in the npm package. It generated error like this in ViteJS project: Failed to resolve import "../../../images/point.gif" from "../core/dist/esm/view/handler/ConstraintHandler.js". Does the file exist? This gif import had been introduced to make `Anchors.stories.js` retrieve the gif file. Configuring `imageBasePath` as already done in other stories fixes the issue. Don't export EditorCodec and StylesheetCodec as they generate errors. This is a temporary solution to avoid error in dependent project (at least, with ViteJS projects).
2022-07-05 06:08:25 +00:00
"description": "maxGraph is a fully client side JavaScript diagramming library that uses SVG and HTML for rendering.",
Refactored everything...
2021-09-07 09:07:27 +00:00
"homepage": "https://github.com/maxGraph/maxGraph",
Update package.json
2017-12-14 13:42:29 +00:00
"repository": {
"type": "git",
Refactored everything...
2021-09-07 09:07:27 +00:00
"url": "git+https://github.com/maxGraph/maxGraph"
Update package.json
2017-12-14 13:42:29 +00:00
},
Added Gruntfile and package.json for npm install; updated .gitignore
2017-08-08 14:13:24 +00:00
"bugs": {
Refactored everything...
2021-09-07 09:07:27 +00:00
"url": "https://github.com/maxGraph/maxGraph/issues"
Added Gruntfile and package.json for npm install; updated .gitignore
2017-08-08 14:13:24 +00:00
},
chore: use npm workspaces (#273) `maxGraph` was using `lerna` v4 to build and only used its "build workspaces" support, not the "publishing" support as we only published a single package and it is done manually, without using `lerna`. The support for packages in `lerna` was removed in version 7. See https://github.com/lerna/lerna/releases/tag/7.0.0 and https://lerna.js.org/docs/legacy-package-management. So, start using npm workspaces as we don't need to manage the publishing of several packages for now. This will allow to do more reproducible builds by locking dependencies with a `package-lock.json` file. This didn't work well with `lerna` v4 and had been disabled.
2023-12-04 02:25:41 +00:00
"workspaces": [
"./packages/*"
],
Update package.json
2017-12-14 13:42:29 +00:00
"scripts": {
- Restructure into a monorepo. - Add Storybook to packages. - Remove circular dependencies.
2021-04-15 04:09:10 +00:00
"dev": "node ./scripts/dev",
chore: configure eslint (#123) Added `eslint` to project and configured it. The fixes will be applied later. ``` Found 1855 problems (709 errors, 1146 warnings) 🙈 628 errors and 291 warnings potentially fixable with the `--fix` option. ```
2022-10-23 07:41:41 +00:00
"lint": "eslint packages/**/**.ts",
"lint:fix": "eslint --fix packages/**/**.ts",
"prettier": "prettier --write packages/*/src/**/*.ts"
Update package.json
2017-12-14 13:42:29 +00:00
},
3.9.2 release
2018-02-28 22:01:56 +00:00
"devDependencies": {
chore: configure eslint (#123) Added `eslint` to project and configured it. The fixes will be applied later. ``` Found 1855 problems (709 errors, 1146 warnings) 🙈 628 errors and 291 warnings potentially fixable with the `--fix` option. ```
2022-10-23 07:41:41 +00:00
"@typescript-eslint/eslint-plugin": "^5.39.0",
"@typescript-eslint/parser": "^5.39.0",
chore: add missing eslint deps
2022-10-29 19:49:23 +00:00
"eslint": "^8.26.0",
"eslint-config-prettier": "^8.5.0",
"eslint-plugin-import": "^2.26.0",
chore: configure eslint (#123) Added `eslint` to project and configured it. The fixes will be applied later. ``` Found 1855 problems (709 errors, 1146 warnings) 🙈 628 errors and 291 warnings potentially fixable with the `--fix` option. ```
2022-10-23 07:41:41 +00:00
"prettier": "^2.7.1",
chore!: only include ESM in the npm package (#266) Get rid of the UMD bundle: not pratical, not minimified so not ready for production, nor for reuse. This lets remove the webpack build which was not used anymore. - core build: everything is done with tsc and simplify pack - remove webpack configuration - Move typedoc in the package where it is used (make it easier to detect usage) - remove unused dependencies: - better-docs (use typedoc instead) - webpack loaders (css, file, style, url) - babel - circular-dependency-plugin (webpack plugin) - webpack - cross-env - core build: tsc only BREAKING CHANGE: the UMD bundle is no more provided in the npm package
2023-12-03 15:51:40 +00:00
"typescript": "^4.9.5"
chore: force usage of a recent @types/node version (#143) Use a recent version of `@types/node` that works with TypeScript 4.9, older versions have types issues.
2022-11-22 06:03:48 +00:00
},
"overrides": {
"@types/node": "^16.18.0"
chore: improve the configuration to build the npm package (#87) Root and all package.json files - Fix license, version and authors - Remove the non-relevant .npmignore file at the project. It was designed for mxgraph, the whole directory structure changed, and we don't plan to publish the root package `core` package - Generate type definition and javascript files for ESM output - dedicated folder for `esm` and `types` in the `dist` folder to clearly separate concerns - exported in the package.json - Add npm script for `npm pack` configuration - Drop the `postinstall` npm script that built the `core` bundle. It would have been run when the package is installed in dependent projects at dependencies install. And it would have failed as it tries to build the project from TypeScript sources that are not available in the npm package. fix: ConstraintHandler now loads image as everywhere else in the code using `Client.imageBasePath` Using import doesn't work as the image is not available in the npm package. It generated error like this in ViteJS project: Failed to resolve import "../../../images/point.gif" from "../core/dist/esm/view/handler/ConstraintHandler.js". Does the file exist? This gif import had been introduced to make `Anchors.stories.js` retrieve the gif file. Configuring `imageBasePath` as already done in other stories fixes the issue. Don't export EditorCodec and StylesheetCodec as they generate errors. This is a temporary solution to avoid error in dependent project (at least, with ViteJS projects).
2022-07-05 06:08:25 +00:00
}
Added Gruntfile and package.json for npm install; updated .gitignore
2017-08-08 14:13:24 +00:00
}